[pve-devel] [PATCH-SERIES qemu-server v2 0/4] migration: reduce friction with nets-host-mtu

[Fiona Ebner <f.ebner@proxmox.com>]

Changes in v2:
* avoid re-introducing breakage if param is actually required

The introduction of the nets-host-mtu migration parameter causes some
friction and requires users to upgrade nodes. In Proxmox VE 9, this
cannot easily be avoided, because the default behavior of inheriting
the MTU from the bridge means, that most migrations are potentially
problematic if not using the parameter. Still, more context is given
to the error so users know they'll need to upgrade.

If both, source and target are on Proxmox VE 8, most migrations are
not affected, only when the MTU parameter is explicitly set to
"inherit from bridge". To reduce friction there, the nets-host-mtu
parameter is only used if such a VirtIO-net device is present.


master:

Fiona Ebner (2):
  migration: tell users to upgrade if nets-host-mtu is not supported
  migration: remove unused variable

 src/PVE/QemuMigrate.pm | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)


stable-bookworm:

Fiona Ebner (2):
  migration: only use nets-host-mtu for PVE 8 target if actually
    required
  migration: tell users to upgrade if nets-host-mtu is required but not
    supported

 src/PVE/QemuMigrate.pm | 14 +++++++++++---
 src/PVE/QemuServer.pm  |  3 ++-
 2 files changed, 13 insertions(+), 4 deletions(-)


-- 
2.47.2



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