* [pve-devel] [PATCH qemu-server 0/1] fix #6828: remote migration: bump timeout for writing configuration to accommodate volume activation
@ 2025-10-01 15:01 Fiona Ebner
2025-10-01 15:01 ` [pve-devel] [PATCH qemu-server 1/1] " Fiona Ebner
0 siblings, 1 reply; 2+ messages in thread
From: Fiona Ebner @ 2025-10-01 15:01 UTC (permalink / raw)
To: pve-devel
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.
qemu-server:
Fiona Ebner (1):
fix #6828: remote migration: bump timeout for writing configuration to
accommodate volume activation
src/PVE/QemuMigrate.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Summary over all repositories:
1 files changed, 1 insertions(+), 1 deletions(-)
--
Generated by git-murpp 0.5.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
* [pve-devel] [PATCH qemu-server 1/1] fix #6828: remote migration: bump timeout for writing configuration to accommodate volume activation
2025-10-01 15:01 [pve-devel] [PATCH qemu-server 0/1] fix #6828: remote migration: bump timeout for writing configuration to accommodate volume activation Fiona Ebner
@ 2025-10-01 15:01 ` Fiona Ebner
0 siblings, 0 replies; 2+ messages in thread
From: Fiona Ebner @ 2025-10-01 15:01 UTC (permalink / raw)
To: pve-devel
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 <f.ebner@proxmox.com>
---
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
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-10-01 15:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-10-01 15:01 [pve-devel] [PATCH qemu-server 0/1] fix #6828: remote migration: bump timeout for writing configuration to accommodate volume activation Fiona Ebner
2025-10-01 15:01 ` [pve-devel] [PATCH qemu-server 1/1] " Fiona Ebner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox