From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH guest-common 2/4] storage tunnel: disk migration: bump timeout for image check after import
Date: Tue, 9 Jun 2026 16:28:47 +0200 [thread overview]
Message-ID: <20260609142858.1063820-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20260609142858.1063820-1-f.ebner@proxmox.com>
As reported in the enterprise support, the 'query-disk-import' command
can time out (for a large disk/busy system) for an offline remote
migration, when the target storage is directory-based. The
'query-disk-import' command will call file_size_info() when the import
is finished to check the image and 10 seconds might not be enough
there. To mitigate the issue, bump the timeout to 1 minute.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/StorageTunnel.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/StorageTunnel.pm b/src/PVE/StorageTunnel.pm
index 864aa0e..37a9842 100644
--- a/src/PVE/StorageTunnel.pm
+++ b/src/PVE/StorageTunnel.pm
@@ -101,7 +101,7 @@ sub storage_migrate {
# wait for the remote process to finish
my $new_volid;
- while ($res = PVE::Tunnel::write_tunnel($tunnel, 10, 'query-disk-import')) {
+ while ($res = PVE::Tunnel::write_tunnel($tunnel, 60, 'query-disk-import')) {
if ($res->{status} eq 'pending') {
if (my $msg = $res->{msg}) {
$log->('info', "disk-import: $msg\n");
--
2.47.3
next prev parent reply other threads:[~2026-06-09 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 14:28 [PATCH-SERIES guest-common/qemu-server 0/4] remote migration (and drive mirror) improvements Fiona Ebner
2026-06-09 14:28 ` [PATCH guest-common 1/4] storage tunnel: query disk import: adapt to current signature for file_size_info() Fiona Ebner
2026-06-09 14:28 ` Fiona Ebner [this message]
2026-06-09 14:28 ` [PATCH qemu-server 3/4] remote migration: mtunnel: avoid warning from superfluous call for removing dbus-vmstate Fiona Ebner
2026-06-09 14:28 ` [PATCH qemu-server 4/4] block job: mirror: use correct unit for logging bandwidth limit 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=20260609142858.1063820-3-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.