From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server master v2 1/4] migration: tell users to upgrade if nets-host-mtu is not supported
Date: Tue, 9 Sep 2025 11:16:57 +0200 [thread overview]
Message-ID: <20250909091918.32254-2-f.ebner@proxmox.com> (raw)
In-Reply-To: <20250909091918.32254-1-f.ebner@proxmox.com>
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.
Suggested-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/QemuMigrate.pm | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/PVE/QemuMigrate.pm b/src/PVE/QemuMigrate.pm
index 4381b542..8fbabdfa 100644
--- a/src/PVE/QemuMigrate.pm
+++ b/src/PVE/QemuMigrate.pm
@@ -1053,6 +1053,7 @@ sub phase2_start_local_cluster {
};
my $target_replicated_volumes = {};
+ my $target_nets_host_mtu_not_supported;
# Note: We try to keep $spice_ticket secret (do not pass via command line parameter)
# instead we pipe it through STDIN
@@ -1110,11 +1111,16 @@ sub phase2_start_local_cluster {
},
errfunc => sub {
my $line = shift;
+ $target_nets_host_mtu_not_supported = 1
+ if $line =~ m/^Unknown option: nets-host-mtu/;
$self->log('info', "[$self->{node}] $line");
},
noerr => 1,
);
+ die "node $self->{node} is too old for preserving VirtIO-net MTU, please upgrade\n"
+ if $target_nets_host_mtu_not_supported;
+
die "remote command failed with exit code $exitcode\n" if $exitcode;
die "unable to detect remote migration address\n"
--
2.47.2
_______________________________________________
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-09-09 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 9:16 [pve-devel] [PATCH-SERIES qemu-server v2 0/4] migration: reduce friction with nets-host-mtu Fiona Ebner
2025-09-09 9:16 ` Fiona Ebner [this message]
2025-09-09 9:16 ` [pve-devel] [PATCH qemu-server master v2 2/4] migration: remove unused variable Fiona Ebner
2025-09-09 9:16 ` [pve-devel] [PATCH qemu-server stable-bookworm v2 3/4] migration: only use nets-host-mtu for PVE 8 target if actually required Fiona Ebner
2025-09-09 9:17 ` [pve-devel] [PATCH qemu-server stable-bookworm v2 4/4] migration: tell users to upgrade if nets-host-mtu is required but not supported Fiona Ebner
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=20250909091918.32254-2-f.ebner@proxmox.com \
--to=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox