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 EFAB01FF16B for ; Tue, 29 Jul 2025 08:06:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C62523FBC7; Tue, 29 Jul 2025 08:07:47 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner Date: Tue, 29 Jul 2025 08:05:22 +0200 Message-ID: <175376912047.1862573.10339598802085429511.b4-ty@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: 1753769225326 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH-SERIES qemu-server 0/3] fix migration status handling (for 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" On Mon, 28 Jul 2025 16:30:30 +0200, Fiona Ebner wrote: > There are some states that 'query-migrate' can return [0] which are > not properly handled by Proxmox VE yet. > > In particular, as reported in the community forum [1], with QEMU 10.0, > the 'device' status can be present with migration parameters used by > Proxmox VE. > > [...] Got already positive feedback in the forum, so: Applied, thanks! FWIW, might be worth to transform the regex to a hash and lc() the key before checking. Seems also a bit odd to me that the regex is using multiline, is that really needed here? But all pre-existing and not really hurting, so really not high priority to check. [1/3] migration: status check: order states in regex alphabetically commit: d3842716a1156a99b937af9c8f89ea43defff13d [2/3] migration: handle 'device' migration status newly present in QEMU 10.0+ commit: 34d03f914821479515272df79792ab3ae17a1c06 [3/3] migration: handle 'cancelling' and 'wait-unplug' status commit: c106f1326daec73677aa33ec5091ac70fe9e6789 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel