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 6444E1FF142 for ; Fri, 22 May 2026 15:21:56 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 32A53BB50; Fri, 22 May 2026 15:21:56 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: [PATCH qemu-server 1/3] cpu flags: include Hyper-V enlightenment flags in supported flags Date: Fri, 22 May 2026 15:21:20 +0200 Message-ID: <20260522132122.712794-2-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260522132122.712794-1-a.bied-charreton@proxmox.com> References: <20260522132122.712794-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.134 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 Message-ID-Hash: JCQP7YA44CN7PM6YGOQ6T7MHAIWP4DDP X-Message-ID-Hash: JCQP7YA44CN7PM6YGOQ6T7MHAIWP4DDP 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: QEMU advertises the Hyper-V enlightenment flags [0] through a different CPUID range, which query-cpu-model-expansion does not cover by default. This leads to query_supported_cpu_flags reporting the hv-* flags as unsupported [1] even though some of them are in the VM-specific flags and QEMU would accept them when starting a VM. Enable hv-passthrough in the temporary VM used to query supported flags for KVM, making it advertise support for the hv-* flags as well. [0] https://www.qemu.org/docs/master/system/i386/hyperv.html [1] https://forum.proxmox.com/threads/incorrect-supported-cpu-flags.183722/#post-853902 Signed-off-by: Arthur Bied-Charreton --- src/PVE/QemuServer.pm | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/PVE/QemuServer.pm b/src/PVE/QemuServer.pm index 118f26bc..239b0cab 100644 --- a/src/PVE/QemuServer.pm +++ b/src/PVE/QemuServer.pm @@ -2982,12 +2982,15 @@ sub query_supported_cpu_flags { my $rc = run_command($cmd, noerr => 1, quiet => 0); die "QEMU flag querying VM exited with code " . $rc if $rc; + my $model = { name => $kvm ? 'host' : 'max' }; + $model->{props} = { 'hv-passthrough' => JSON::true } if $kvm; + eval { my $cmd_result = mon_cmd( $fakevmid, 'query-cpu-model-expansion', type => 'full', - model => { name => $kvm ? 'host' : 'max' }, + model => $model, ); my $props = $cmd_result->{model}->{props}; -- 2.47.3