From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 08F696CA3F for ; Tue, 30 Mar 2021 18:00:06 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id ED6E32CC7D for ; Tue, 30 Mar 2021 18:00:05 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id A0CC62CC6B for ; Tue, 30 Mar 2021 18:00:04 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 5B8CE45980 for ; Tue, 30 Mar 2021 18:00:04 +0200 (CEST) From: Stefan Reiter To: pve-devel@lists.proxmox.com Date: Tue, 30 Mar 2021 17:59:52 +0200 Message-Id: <20210330155952.16389-2-s.reiter@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20210330155952.16389-1-s.reiter@proxmox.com> References: <20210330155952.16389-1-s.reiter@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.019 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [qemuserver.pm] Subject: [pve-devel] [PATCH qemu-server 2/2] increase timeout for QMP block_resize X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Mar 2021 16:00:06 -0000 In testing this usually completes almost immediately, but in theory this is a storage/IO operation and as such can take a bit to finish. It's certainly not unthinkable that it might take longer than the default *3 seconds* we've given it so far. Make it a minute. Signed-off-by: Stefan Reiter --- Optional for the fix, but seems like a good idea. PVE/QemuServer.pm | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm index 1c0b5c2..f9379f6 100644 --- a/PVE/QemuServer.pm +++ b/PVE/QemuServer.pm @@ -4291,8 +4291,13 @@ sub qemu_block_resize { my $padding = (1024 - $size % 1024) % 1024; $size = $size + $padding; - mon_cmd($vmid, "block_resize", device => $deviceid, size => int($size)); - + mon_cmd( + $vmid, + "block_resize", + device => $deviceid, + size => int($size), + timeout => 60, + ); } sub qemu_volume_snapshot { -- 2.20.1