From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 9E54B1FF14F for ; Wed, 17 Jun 2026 10:06:36 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0ABC918C36; Wed, 17 Jun 2026 10:06:33 +0200 (CEST) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pve-devel@lists.proxmox.com, Fiona Ebner Subject: applied-series [PATCH-SERIES guest-common/qemu-server 0/4] remote migration (and drive mirror) improvements Date: Wed, 17 Jun 2026 10:05:53 +0200 Message-ID: <178168326937.141369.8348103467019055716.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260609142858.1063820-1-f.ebner@proxmox.com> References: <20260609142858.1063820-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1781683502229 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: XGELPKPD5WS6LFWL445MNACKMLH7RJQW X-Message-ID-Hash: XGELPKPD5WS6LFWL445MNACKMLH7RJQW X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 09 Jun 2026 16:28:45 +0200, Fiona Ebner wrote: > 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. > > [...] Applied, thanks! [1/4] storage tunnel: query disk import: adapt to current signature for file_size_info() commit: 93f947496d758ed1202caf51073f557460c5c5f5 [2/4] storage tunnel: disk migration: bump timeout for image check after import commit: ce94240c0815f86ccc787e6bb3ce29621b98208f [3/4] remote migration: mtunnel: avoid warning from superfluous call for removing dbus-vmstate commit: 956489c5af90edbb739bc983f6f30b00fc0f92a2 [4/4] block job: mirror: use correct unit for logging bandwidth limit commit: 37e87e7ff07c4cac1978bf6e4bb5a0c232efa09a Best regards, -- Fabian Grünbichler