Hi,
interesting but nothing obvious comes directly to my mind.
It is great that you identified that the device driver virtio/rtl8139 makes a
difference.
Lets start there to think about it.
Traffic for rtl8139 will always go to host-userspace for device emulation and
flow on from there.
With virtio in comparison I think the default if available will be vhost-net
which will handle things in the host kernel and should not (tm) but might
behave differently.
While vhost-net is usually better for efficiency and performance lets check if
that makes the difference.
Please set back the Ubuntu VM to virtio but then in addition to
<model type="virtio"/>
also set
<driver name="qemu"/>
The default is "try vhost but if failing (e.g. module not present) fall
back to qemu"; but setting qemu explicitly there will force it to use
the userspace backend.
Please let me know how virtio behaves in that case.
If we can move this from rtl8139-vs-virtio to virtio with/without vhost that
already would be a good step to get closer to the root cause.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
