The 'config' command will lead to volume activation being done for the referenced volumes. This is because the 'config' handler in the mtunnel API endpoint calls into the update_vm_api() function, which uses the create_disks() function, which is also used for existing disks. In create_disks(), each volume is activated to do an existence/basic sanity check by querying its size.
There is no requirement to be fast when handling the 'config' command during remote migration. Since there could be many disks for a given VM, allow for up to 2 minutes instead of just 10 seconds. Signed-off-by: Fiona Ebner <[email protected]> --- src/PVE/QemuMigrate.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/QemuMigrate.pm b/src/PVE/QemuMigrate.pm index 7093c41e..da5b4b78 100644 --- a/src/PVE/QemuMigrate.pm +++ b/src/PVE/QemuMigrate.pm @@ -922,7 +922,7 @@ sub phase1_remote { 'firewall-config' => $fw_conf_str, }; - PVE::Tunnel::write_tunnel($self->{tunnel}, 10, 'config', $params); + PVE::Tunnel::write_tunnel($self->{tunnel}, 120, 'config', $params); } sub phase1_cleanup { -- 2.47.3 _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
