This message was deleted.

@wide-farmer-46260 yes qemu-ga is responsible for notifying the ip addr to the vmi and then UI is updated from vmi. Also did you try the same on some official cloud img, for eg https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img

is it just that Harvester is not showing the IP address or does the VM not get an IP address (if DHCP) and/or is IP working?

I figured out the issue. Sorry for long response. Issue was that Harvester was not showing the IP address even though the VM had an ip address. The IP address was not being shown due to the qemu-guest-agent not getting installed on boot by cloud init. Cloud init was not installing qemu-guest-agent because I found out cloud init was disabling itself on boot causing the cloud-init scripts to never get executed. Cloud-init was disabling itself because in the boot process of cloud-init (explained in Cloud Init's docs here https://cloudinit.readthedocs.io/en/latest/explanation/boot.html#generator ) it runs a tool called ds-identify during the first "Detect" stage. This stage basically determines what environment you're running cloud init in and configures it to use that environment's cloud init datasource. Here is a list of available cloud init data sources https://cloudinit.readthedocs.io/en/latest/reference/datasources.html . This is why my image was working in AWS environments because cloud init could discover the AWS datasource. In the event that cloud init DOES NOT find a datasource like in the case of running in Harvester, cloud-init disables itself on boot. The fix to my issue was that I had to configure cloud init to boot even in the case of it not finding a datasource. This can be done via kernel parameter or cloud init configuration file. Documentation on how to configure cloud init is here https://github.com/canonical/cloud-init/blob/main/tools/ds-identify After I configured cloud-init correctly, I was able to boot a VM in harvester with that custom image, cloud init started and installed the qemu-guest-agent package, and then an IP was received in the Harvester UI for my VM.

@wide-farmer-46260 what exactly is the fix for the cloud init configuration file? 🙂

@fierce-magazine-18543 I had to append this to the

GRUB_CMDLINE_LINUX

line in my

/etc/default/grub

file on my premade image

ci.di.policy=search,found=all,maybe=all,notfound=enabled

I see, thanks! I will need to experiment more on cloud images. It is still a bit new to me. Have only used it in my previous instance, without doing anything custom.