From: Fiona Ebner <f.ebner@proxmox.com>
To: Friedrich Weber <f.weber@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server v2 1/3] cpu config: disable vmx-mbec flag for machine versions < 11.0
Date: Mon, 13 Jul 2026 14:48:38 +0200 [thread overview]
Message-ID: <900bc845-b66e-4c8f-bf30-539c5dba0cbd@proxmox.com> (raw)
In-Reply-To: <bf9c73f2-224e-4821-b8d9-a5ab44a00f64@proxmox.com>
Am 13.07.26 um 2:46 PM schrieb Friedrich Weber:
> On 13/07/2026 14:40, Fiona Ebner wrote:
>> 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. Note that the vmx-mbec flag will
>> automatically be enabled if both QEMU (since 11.0) and the kernel
>> (since 7.0.0-3-pve) support it, but this is incorrect from a machine
>> version perspective, since the flag was enabled before. While there
>
> Should this be "since the flag *not* enabled before"?
Yes, good catch! Maybe even "the feature was not available before",
since the flag did not even exist yet.
next prev parent reply other threads:[~2026-07-13 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 12:40 [PATCH-SERIES qemu-server v2 0/3] cpu config: disable APICv for Windows 11/2022/2025 to mitigate issues with VBS Fiona Ebner
2026-07-13 12:40 ` [PATCH qemu-server v2 1/3] cpu config: disable vmx-mbec flag for machine versions < 11.0 Fiona Ebner
2026-07-13 12:46 ` Friedrich Weber
2026-07-13 12:48 ` Fiona Ebner [this message]
2026-07-13 12:40 ` [PATCH qemu-server v2 2/3] cpu config: use $version_guard rather than passing $machine_version Fiona Ebner
2026-07-13 12:40 ` [PATCH qemu-server v2 3/3] cpu config: disable APICv for Windows 11/2022/2025 to mitigate issues with VBS Fiona Ebner
2026-07-15 8:21 ` superseded: [PATCH-SERIES qemu-server v2 0/3] " 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=900bc845-b66e-4c8f-bf30-539c5dba0cbd@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.weber@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