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 4826A1FF13B for ; Wed, 03 Jun 2026 09:09:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 26F1A374E0; Wed, 3 Jun 2026 09:09:32 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: [PATCH pve-qemu v3 0/2] include Hyper-V enlightenments in CPUID flags list Date: Wed, 3 Jun 2026 09:07:34 +0200 Message-ID: <20260603070857.184709-1-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.132 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an 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. [parse-cpu-flags.pl] Message-ID-Hash: YBKSRMBZOI6FYYIPH2N4XIDWZACCUWIW X-Message-ID-Hash: YBKSRMBZOI6FYYIPH2N4XIDWZACCUWIW X-MailFrom: abied-charreton@jett.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: In the context of custom CPU models, the hv-* flags are not part of the base list at all. This means they don't show up in the selector, not even as unsupported, making it impossible to set them without manually editing cpu-models.conf. Until now, this base list was generated from the '-cpu help' output at pve-qemu-kvm build time [0]. The first patch refactors the script parsing CPU flags to additionally include the Hyper-V enlightenments by sourcing the flags from the qom-list-properties QMP command instead, blacklisting unwanted properties this new source would add. The second patch pins the resulting flag list into the repository and fails the build on any divergence, as already done for CPU models. This ensures flag additions/removals are surfaced for review on QEMU bumps. [0] https://git.proxmox.com/?p=pve-qemu.git;a=blob;f=debian/rules;h=c90db29b0f03568224b1c79431bce2b753283a4d;hb=refs/heads/master#l126 Changes since v2 (thanks @Fiona): * Rename $blacklist to $filtered_props * Die if QMP greeting does not have the expected format * Expect the CPU typename as a CLI parameter and use max-x86_64-cpu instead of host-x86_64-cpu for portability * Group blacklist entries by typename * Fix some style errors and remove dead code Arthur Bied-Charreton (2): build: include Hyper-V enlightenments in CPUID flags list build: fail when recognized CPUID flags list changes debian/parse-cpu-flags.pl | 144 ++++++++- debian/recognized-CPUID-flags-x86_64 | 429 +++++++++++++++++++++++++++ debian/rules | 6 +- 3 files changed, 563 insertions(+), 16 deletions(-) create mode 100644 debian/recognized-CPUID-flags-x86_64 -- 2.47.3