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 47E5D1FF146 for ; Tue, 26 May 2026 10:43:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 81A8616C90; Tue, 26 May 2026 10:43:18 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com, Arthur Bied-Charreton Subject: applied: [PATCH qemu-server 1/3] cpu flags: include Hyper-V enlightenment flags in supported flags Date: Tue, 26 May 2026 10:43:01 +0200 Message-ID: <177978495657.52909.9447298169275857943.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260522132122.712794-2-a.bied-charreton@proxmox.com> References: <20260522132122.712794-1-a.bied-charreton@proxmox.com> <20260522132122.712794-2-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779784970418 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.009 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 Message-ID-Hash: 2PMJ44I4ZIAMRWGJD3FOSS4BRRMZMRBK X-Message-ID-Hash: 2PMJ44I4ZIAMRWGJD3FOSS4BRRMZMRBK X-MailFrom: f.ebner@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: On Fri, 22 May 2026 15:21:20 +0200, Arthur Bied-Charreton wrote: > 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. Applied, thanks! [1/3] cpu flags: include Hyper-V enlightenment flags in supported flags commit: 698550c2682ed8ab20c3d41a56be79b11063c05a