I must be missing something obvious. I could not get a single new vm to work. Using the latest Harvester version with 3 powerful physical test nodes here. I created a new image in Harvester UI with URL from https://cloud-images.ubuntu.com/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img, I think it is the same as Harvester doc. I created a new vm vlan (could not get dhcp to work, and went with manual/static, with CIDR and Gateway IP configured, with L2VlanNetwork on default mgmt cluster network). The new VM boots up, I could see login prompt in its UI serial console. But the VM did not get any IP assigned. Is this expected?

Need install qemu-guest-agent in vm to report IP to kubevirt

hmm, I worried that the problem is the VM did not get an IP assigned, from serial console log, I could see the VM tried to talk to some internet hostnames but failed. How could I verify that this new VM got assigned an IP correctly in Harvester K8S command prompt via kubectl command? If the VM did not get an IP assigned correctly, it won’t be able to install the package even inside on-prem network.

You can check the status of vm instance via

kubectl get vmi

VM status is

Ready=True

, but in this command output, the

IP

field is showing up as empty. I tried

kubectl describe vmi my_vm_name_here | grep -E -i '(ip|add)'

, and there’s no output. Is this expected?

What is the vlanid in your vm network？or maybe you can try the https://docs.harvesterhci.io/v1.1/networking/harvester-network#untagged-network

vlanid is 450. Does a particular vlanid matter in this case? The vlan is tagged vlan, so untagged vlan won’t help.