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 4B6D51FF183 for ; Wed, 10 Sep 2025 13:12:20 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B30A71EE42; Wed, 10 Sep 2025 13:12:24 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Date: Wed, 10 Sep 2025 13:11:35 +0200 Message-ID: <175750269447.2442735.17213833793360376278.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250909091918.32254-2-f.ebner@proxmox.com> References: <20250909091918.32254-1-f.ebner@proxmox.com> <20250909091918.32254-2-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1757502686727 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.029 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [PATCH qemu-server master v2 1/4] migration: tell users to upgrade if nets-host-mtu is not supported 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 Tue, 09 Sep 2025 11:16:57 +0200, Fiona Ebner wrote: > In Proxmox VE 9, the default behavior for VirtIO network devices is to > inherit the MTU from the bridge. This means that most migrations are > potentially problematic when the nets-host-mtu parameter is not set, > see commit 20c91f7f ("migration: preserve host_mtu for virtio-net > devices"). While setting the parameter could be avoided in some cases, > the information what MTU the target node bridges have is not readily > available. Upgrading is already required to avoid actual problematic > cases, so just tell people to upgrade when the target does not support > preserving the VirtIO-net MTU yet in all cases. > > [...] Applied, thanks! [1/4] migration: tell users to upgrade if nets-host-mtu is not supported commit: 67d8d092b11c9c8dbb071f705977858416584989 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel