From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES qemu-server 0/2] cpu config: disable APICv for Windows 11/2022/2025 to mitigate issues with VBS
Date: Thu, 9 Jul 2026 15:41:59 +0200 [thread overview]
Message-ID: <20260709134211.199744-1-f.ebner@proxmox.com> (raw)
As reported in the community forum [0] and enterprise support, Windows
with MBEC and VBS can have issues on certain Intel CPUs, leading to
guest freezes and 100% CPU usage. The detection/enabling of APICv
support in Windows was determined to be related. Disabling
vmx-apicv-vid and/or vmx-apicv-register mitigates the issue. Disable
both flags starting with a bumped 11.0+pve2 machine version for
consistency.
[0]: https://forum.proxmox.com/threads/184178
What still would be nice to check is if the issue also happens with a
non-host model with nested-virt/vmx present. Otherwise we might want
to restrict removing the flags to the host model.
qemu-server:
Fiona Ebner (2):
cpu config: use $version_guard rather than passing $machine_version
cpu config: disable APICv for Windows 11/2022/2025 to mitigate issues
with VBS
src/PVE/QemuServer.pm | 2 +-
src/PVE/QemuServer/CPUConfig.pm | 33 +++++++++++++------
src/PVE/QemuServer/Machine.pm | 3 +-
src/test/cfg2cmd/win11-host-11.0+pve2.conf | 4 +++
.../cfg2cmd/win11-host-11.0+pve2.conf.cmd | 26 +++++++++++++++
5 files changed, 56 insertions(+), 12 deletions(-)
create mode 100644 src/test/cfg2cmd/win11-host-11.0+pve2.conf
create mode 100644 src/test/cfg2cmd/win11-host-11.0+pve2.conf.cmd
Summary over all repositories:
5 files changed, 56 insertions(+), 12 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-07-09 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 13:41 Fiona Ebner [this message]
2026-07-09 13:42 ` [PATCH qemu-server 1/2] cpu config: use $version_guard rather than passing $machine_version Fiona Ebner
2026-07-09 13:42 ` [PATCH qemu-server 2/2] cpu config: disable APICv for Windows 11/2022/2025 to mitigate issues with VBS Fiona Ebner
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=20260709134211.199744-1-f.ebner@proxmox.com \
--to=f.ebner@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