[pve-devel] [PATCH docs/manager/qemu-server v2 0/3] Make VirtIO network devices always inherit MTU from bridge
Stefan Hanreich
s.hanreich at proxmox.com
Thu Apr 17 12:48:52 CEST 2025
The current default behavior for VirtIO network devices is to default to 1500
MTU, unless otherwise specified. This is inconvenient in cases where the MTU is
not the default value (e.g. for VXLAN VNets or bridges with jumbo frames).
Containers already inherit the MTU of the bridge, if not set, so change the
behavior of VMs to be more in line with containers. This also makes using
non-standard MTUs more convenient and less error-prone since users do not have
to remember setting the MTU everytime they configure a network device on such a
brige.
Changes from v1:
* better document this behavior
* show better hints in the UI
* improve test case
qemu-server:
Stefan Hanreich (1):
net: pass host_mtu parameter when mtu is unset in netdev config
PVE/QemuServer.pm | 30 ++++++++++++++++--------------
test/cfg2cmd/netdev_vxlan.conf | 7 +++++++
test/cfg2cmd/netdev_vxlan.conf.cmd | 28 ++++++++++++++++++++++++++++
test/run_config2command_tests.pl | 6 ++++++
4 files changed, 57 insertions(+), 14 deletions(-)
create mode 100644 test/cfg2cmd/netdev_vxlan.conf
create mode 100644 test/cfg2cmd/netdev_vxlan.conf.cmd
pve-manager:
Stefan Hanreich (1):
qemu: network: adjust MTU emptyText to match new default behavior
www/manager6/qemu/NetworkEdit.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
pve-docs:
Stefan Hanreich (1):
qm: document new default behavior for mtu setting
qm.adoc | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
Summary over all repositories:
6 files changed, 61 insertions(+), 19 deletions(-)
--
Generated by git-murpp 0.8.0
More information about the pve-devel
mailing list