Maybe it fast-pathes around something when both are virtio. But you said you set driver=qemu and it still was broken with virtio, I didn't expect that.
I have given it a few tries with a similar setup among a few VMs but haven't seen the issue myself. You probably want to report that upstream to get more eyes/brains onto that case. But with the case as-is atm I'm not really sure if that would be better started at libvirt [1] or qemu [2]. Maybe start with one and if redirected from there go to the other? I'm subscribed on both, but would appreciate if you could add here a link to the thread you started on the ML to find it again later. [1]: https://www.redhat.com/mailman/listinfo/libvir-list [2]: https://lists.nongnu.org/mailman/listinfo/qemu-devel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853489 Title: Ignoring the default NAT when using the virtio adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
