all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs/manager/qemu-server v3 0/3] Make VirtIO network devices inherit MTU from bridge by default
Date: Thu, 17 Jul 2025 19:50:09 +0200	[thread overview]
Message-ID: <20250717175012.606372-1-s.hanreich@proxmox.com> (raw)

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 v2:
* rebase on top of re-formatted code
* fix tests with new qemu version

Changes from v1:
* better document this behavior
* show better hints in the UI
* improve test case

qemu-server:

Stefan Hanreich (1):
  net: automatically set host_mtu to bridge mtu for virtio netdevs

 src/PVE/QemuServer.pm                  | 30 ++++++++++++++------------
 src/PVE/QemuServer/Network.pm          |  3 ++-
 src/test/cfg2cmd/netdev_vxlan.conf     |  7 ++++++
 src/test/cfg2cmd/netdev_vxlan.conf.cmd | 28 ++++++++++++++++++++++++
 src/test/run_config2command_tests.pl   |  6 ++++++
 5 files changed, 59 insertions(+), 15 deletions(-)
 create mode 100644 src/test/cfg2cmd/netdev_vxlan.conf
 create mode 100644 src/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:
  7 files changed, 63 insertions(+), 20 deletions(-)

-- 
Generated by git-murpp 0.8.0

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


             reply	other threads:[~2025-07-17 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17 17:50 Stefan Hanreich [this message]
2025-07-17 17:50 ` [pve-devel] [PATCH qemu-server v3 1/1] net: automatically set host_mtu to bridge mtu for virtio netdevs Stefan Hanreich
2025-07-17 18:39   ` Thomas Lamprecht
2025-07-17 17:50 ` [pve-devel] [PATCH pve-manager v3 1/1] qemu: network: adjust MTU emptyText to match new default behavior Stefan Hanreich
2025-07-17 18:39   ` Thomas Lamprecht
2025-07-17 17:50 ` [pve-devel] [PATCH pve-docs v3 1/1] qm: document new default behavior for mtu setting Stefan Hanreich
2025-07-17 18:39   ` Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250717175012.606372-1-s.hanreich@proxmox.com \
    --to=s.hanreich@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal