Maxime Coquelin <maxime.coque...@redhat.com> writes: > This series implements Virtio spec update from Aaron Conole which > defines a way for the host to expose its max MTU to the guest. > > Changes since RFC v1: > --------------------- > - Rebased on top of v2.8.0-rc0 (2.7.90) > - Write MTU unconditionnaly in netcfg to avoid memory leak (Paolo) > - Add host_mtu property to be able to disable the feature from QEMU > > Maxime Coquelin (3): > vhost-user: Add new protocol feature MTU > vhost-net: Add new MTU feature support > virtio-net: Add MTU feature support > > hw/net/vhost_net.c | 11 +++++++++++ > hw/net/virtio-net.c | 14 ++++++++++++++ > hw/virtio/vhost-user.c | 11 +++++++++++ > include/hw/virtio/vhost.h | 1 + > include/hw/virtio/virtio-net.h | 1 + > include/net/vhost_net.h | 2 ++ > 6 files changed, 40 insertions(+)
I ran this with a VM, but it seems the offered maximum MTU was of value 0 - is this expected with this version? How can I change the offered value? Sorry, I'm not as familiar with QEMU/libvirt side of the world. -Aaron
