This also appears to affect Debian VMs created from the package openstack-debian-image. It appears that it starts out in HVM mode and then switches to PV drivers mid-way through boot, manifesting with an untagged OVS port in dom0. If I restart the OVS agent that manages OVS ports in dom0, the tag gets placed properly. By then, it's too late for dhcp and cloud-init, so the VM never gets network or metadata.
I suspect that it's because the flags supplied with the image in glance aren't set properly, but I'm still investigating. I thought I remembered reading that you can set something in glance along with the image to define the target hypervisor and virtualization method.
This also appears to affect Debian VMs created from the package openstack- debian- image. It appears that it starts out in HVM mode and then switches to PV drivers mid-way through boot, manifesting with an untagged OVS port in dom0. If I restart the OVS agent that manages OVS ports in dom0, the tag gets placed properly. By then, it's too late for dhcp and cloud-init, so the VM never gets network or metadata.
I suspect that it's because the flags supplied with the image in glance aren't set properly, but I'm still investigating. I thought I remembered reading that you can set something in glance along with the image to define the target hypervisor and virtualization method.