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 A98231FF136 for ; Mon, 18 May 2026 16:00:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3A7DF13F06; Mon, 18 May 2026 16:00:11 +0200 (CEST) Message-ID: <1722944d-fcd5-4b4f-a37e-a9ca345d52e2@proxmox.com> Date: Mon, 18 May 2026 16:00:05 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH qemu-server] cpu config: expose CPU 'level' property required for certain host/guest configurations To: Fiona Ebner , pve-devel@lists.proxmox.com References: <20260518124018.148829-1-f.ebner@proxmox.com> Content-Language: en-US From: David Riley In-Reply-To: <20260518124018.148829-1-f.ebner@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779112793740 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.273 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [cpuconfig.pm,proxmox.com] Message-ID-Hash: RAHPSVDDTXVYVVJGRZ57UUTBAHJNJF2K X-Message-ID-Hash: RAHPSVDDTXVYVVJGRZ57UUTBAHJNJF2K X-MailFrom: d.riley@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: Thanks for sending in this patch. I was able to apply the series without issues. I tested the new `level=30` option by adding it to my .conf for a Windows Server Guest. Checked the output from `qm showcmd ` and was able to verify that the option was set correctly and the default Hyper-V Enlightenments were also still present as expected. Tested-by: David Riley Reviewed-by: David Riley On 5/18/26 2:40 PM, Fiona Ebner wrote: > As reported in the community forum in 2024 [0] already, with somewhat > recent Intel CPUs, Windows guests with Hyper-V enabled will fail to > boot with certain CPU types like 'host' or 'max'. A workaround is > using 'level=30' in the '-cpu' QEMU commandline. The 'level' property > is currently not exposed, so users were forced to use custom 'args', > which means they lose other CPU configuration made by Proxmox VE. > Expose the 'level' setting, so it can be done without custom args. > > While the problem is not new, it will become more common, since > virtualization-based security is being adapted more broadly. > > [0]: https://forum.proxmox.com/threads/131950/post-642093 > > Signed-off-by: Fiona Ebner > --- > src/PVE/QemuServer/CPUConfig.pm | 18 ++++++++++++++++++ > src/test/cfg2cmd/cpu-level.conf | 6 ++++++ > src/test/cfg2cmd/cpu-level.conf.cmd | 26 ++++++++++++++++++++++++++ > 3 files changed, 50 insertions(+) > create mode 100644 src/test/cfg2cmd/cpu-level.conf > create mode 100644 src/test/cfg2cmd/cpu-level.conf.cmd > > > [snip]