So, libvirt knew about some change and picks the right default if you do not specify it. But if you (Openstack in this case) specify virtio-mmio as type, then it fails - is that correct?
The patch in the referred RH-BZ is already in the qemu we have in Artful (and thereby Ocata). So if that is supposed to be the issue there has to be a new one after that fix. Also as I've shown in c#17 (yes it is long sorry) - virtio-mmio works with the bridge that libvirt is usually creating - again my assumption is that it is somehow related to how this bridge is created (openvswitch in your case I assume). So is the real error "network fails when using virtio-mmio on openvswitch set up by openstack"? I have no OVS around to quickly try something around that atm. Would it be reasonable to teach Openstack to not define virtio-mmio in this case? Libvirt will make the right default (hopefully also when driven by Openstack which sets some force options), and just work then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719196 Title: [arm64 ocata] newly created instances are unable to raise network interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1719196/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
