From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 64AE91FF165 for ; Thu, 17 Jul 2025 20:39:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 71257A93A; Thu, 17 Jul 2025 20:40:30 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Date: Thu, 17 Jul 2025 20:39:44 +0200 Message-ID: <175277758217.14406.14913079267800811960.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250717175012.606372-2-s.hanreich@proxmox.com> References: <20250717175012.606372-1-s.hanreich@proxmox.com> <20250717175012.606372-2-s.hanreich@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1752777624259 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.033 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH qemu-server v3 1/1] net: automatically set host_mtu to bridge mtu for virtio netdevs X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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