From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 159E21FF09C for ; Mon, 19 Oct 2026 11:54:26 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 1C88A21707; Mon, 19 Oct 2026 11:53:54 +0200 (CEST) From: Thomas Ellmenreich To: pve-devel@lists.proxmox.com Subject: [PATCH qemu-server 5/5] drive: rescan drives after migrating to different storage Date: Mon, 19 Oct 2026 11:53:46 +0200 Message-ID: <20261019095346.175659-6-t.ellmenreich@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261019095346.175659-1-t.ellmenreich@proxmox.com> References: <20261019095346.175659-1-t.ellmenreich@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792403627827 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.432 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) 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 Message-ID-Hash: OF6DPBF3JFHUVRLR273AT2DTVQFQ455W X-Message-ID-Hash: OF6DPBF3JFHUVRLR273AT2DTVQFQ455W X-MailFrom: t.ellmenreich@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 CC: Thomas Ellmenreich X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: In some cases, migrating to a different storage can change the size of disks due to the underlying granularity of the storage. In the case of a storage with 64MiB granularity, this can increase a 4MiB TPM disk to 64MiB. To avoid out of sync ui, rescan all disks of the migrated vm after such a storage change. The rescan not only adjusts the disk size, but also shows all unused disks that may not have been shown before. Signed-off-by: Thomas Ellmenreich --- src/PVE/QemuMigrate.pm | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/PVE/QemuMigrate.pm b/src/PVE/QemuMigrate.pm index 3845fb41..fe5f422a 100644 --- a/src/PVE/QemuMigrate.pm +++ b/src/PVE/QemuMigrate.pm @@ -1905,6 +1905,18 @@ sub phase3_cleanup { $self->cmd_logerr($cmd, errmsg => "failed to clear migrate lock"); } + if (!$self->{opts}->{remote} && scalar(keys %{ $self->{volume_map} })) { + my $cmd = [@{ $self->{rem_ssh} }, 'qm', 'disk', 'rescan', '--vmid', $vmid]; + eval { + PVE::Tools::run_command( + $cmd, + outfunc => sub { }, + errfunc => sub { $self->log('warn', shift) }, + ); + }; + $self->log('warn', "failed to rescan disks after migration - $@") if $@; + } + if ($self->{opts}->{remote} && $self->{opts}->{delete}) { eval { PVE::QemuServer::destroy_vm($self->{storecfg}, $vmid, 1, undef, 0) }; warn "Failed to remove source VM - $@\n" if $@; -- 2.47.3