From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 4DC0C1FF187 for ; Mon, 28 Jul 2025 16:30:05 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7F3F6362BE; Mon, 28 Jul 2025 16:31:21 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Mon, 28 Jul 2025 16:30:32 +0200 Message-ID: <20250728143042.103045-3-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250728143042.103045-1-f.ebner@proxmox.com> References: <20250728143042.103045-1-f.ebner@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753713038140 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.026 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 Subject: [pve-devel] [PATCH qemu-server 2/3] migration: handle 'device' migration status newly present in QEMU 10.0+ 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: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" The QMP reference docs describe the 'device' status as: > During device serialisation (also known as switchover phase). Before > 9.2, this is only used when (1) in precopy, and (2) when > pre-switchover capability is enabled. After 10.0, this state will > always be present for every migration procedure as the switchover > phase. Since Proxmox VE did not use the pre-switchover capability, it has not been observed before QEMU 10.0. The state is still only reached during block device inactivation, but it will be reached. Reported in the community forum: https://forum.proxmox.com/threads/168619/post-786535 Signed-off-by: Fiona Ebner --- src/PVE/QemuMigrate.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PVE/QemuMigrate.pm b/src/PVE/QemuMigrate.pm index edaf2f25..5b854292 100644 --- a/src/PVE/QemuMigrate.pm +++ b/src/PVE/QemuMigrate.pm @@ -1354,7 +1354,7 @@ sub phase2 { next; } - if (!defined($status) || $status !~ m/^(active|cancelled|completed|failed)$/im) { + if (!defined($status) || $status !~ m/^(active|cancelled|completed|device|failed)$/im) { die $merr if $merr; die "unable to parse migration status '$status' - aborting\n"; } @@ -1394,7 +1394,7 @@ sub phase2 { die "aborting\n"; } - if ($status ne 'active') { + if ($status ne 'active' && $status ne 'device') { $self->log('info', "migration status: $status"); last; } -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel