From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-qemu] parse-cpu-flags: stop filtering out 'pmu'
Date: Tue, 13 Oct 2026 10:31:50 +0200 [thread overview]
Message-ID: <20261013083151.262823-1-a.bied-charreton@proxmox.com> (raw)
'pmu' was excluded from the list of flags in the custom CPU flag dialog
because it is not a CPUID flag (not part of '-cpu help' output).
However, it is a plain boolean property so it fits the [+-]<flag> syntax
from the custom CPU config, and QEMU accepts it when set manually via
'+pmu'.
Windows guests using VBS need a virtual PMU, which is not enabled by
default on many models (EPYC-Turin, EPYC-Genoa, SapphireRapids, and
presumably others I have not tested). This currently requires users to
edit the config by hand since the flag cannot be selected in the UI.
Remove 'pmu' from the blacklist so it shows up in the generated flag
list.
Reported-by: David Riley <d.riley@proxmox.com>
Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
---
debian/parse-cpu-flags.pl | 1 -
1 file changed, 1 deletion(-)
diff --git a/debian/parse-cpu-flags.pl b/debian/parse-cpu-flags.pl
index e680f99..e1af0e8 100755
--- a/debian/parse-cpu-flags.pl
+++ b/debian/parse-cpu-flags.pl
@@ -66,7 +66,6 @@ my $filtered_props = {
'legacy-multi-node' => 1,
lmce => 1,
migratable => 1,
- pmu => 1,
realized => 1,
'start-powered-off' => 1,
'tcg-cpuid' => 1,
--
2.47.3
next reply other threads:[~2026-10-13 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 8:31 Arthur Bied-Charreton [this message]
2026-10-13 9:19 ` [PATCH pve-qemu] parse-cpu-flags: stop filtering out 'pmu' Fiona Ebner
2026-10-13 9:21 ` Arthur Bied-Charreton
2026-10-13 9:53 ` superseded: " Arthur Bied-Charreton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261013083151.262823-1-a.bied-charreton@proxmox.com \
--to=a.bied-charreton@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox