From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v3 1/1] net: automatically set host_mtu to bridge mtu for virtio netdevs
Date: Thu, 17 Jul 2025 20:39:44 +0200 [thread overview]
Message-ID: <175277758217.14406.14913079267800811960.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250717175012.606372-2-s.hanreich@proxmox.com>
On Thu, 17 Jul 2025 19:50:10 +0200, Stefan Hanreich wrote:
> When creating a new network device from the UI and leaving the MTU
> field empty, it defaults to 1500. This is inconvenient in cases where
> the MTU of the bridge is not 1500 and lead to some confusion of users
> [1]. Containers already inherit the bridge MTU when the field is left
> empty, so align the behavior of VMs to be more in line with the more
> convenient behavior of containers.
>
> [...]
Applied, thanks!
[1/1] net: automatically set host_mtu to bridge mtu for virtio netdevs
commit: 84a937c14ac36826b073543f64fe41dbd4a0d55e
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-17 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 17:50 [pve-devel] [PATCH docs/manager/qemu-server v3 0/3] Make VirtIO network devices inherit MTU from bridge by default Stefan Hanreich
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 [this message]
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=175277758217.14406.14913079267800811960.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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.