I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes:
Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine.
I don't know if nameservice not working is by design, but it seems like it should work. The documentation states:
"With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"
And https is not going to work for a raw IP address.
I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes:
-smbios "type=1, serial= ds=nocloud- net;s=https:/ /raw.githubuser content. com/mlyle/ mlyle/master/ cloud-metadata/ linuxtst/"
As documented here:
http:// cloudinit. readthedocs. io/en/latest/ topics/ datasources/ nocloud. html
Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine.
I don't know if nameservice not working is by design, but it seems like it should work. The documentation states:
"With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"
And https is not going to work for a raw IP address.