all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH-SERIES qemu-server v3 0/4] cpu config: enable hv-evmcs for Windows 11/2022/2025 to mitigate issues with VBS
Date: Wed, 15 Jul 2026 13:46:34 +0200	[thread overview]
Message-ID: <s8omrvstqzp.fsf@toolbox> (raw)
In-Reply-To: <20260714104201.71308-1-f.ebner@proxmox.com> (Fiona Ebner's message of "Tue, 14 Jul 2026 12:41:47 +0200")

Fiona Ebner <f.ebner@proxmox.com> writes:

> Changes in v3:
> * Improve commit message in patch 1.
> * Different approach, enable recommended hv-evmcs flag instead of
>   disabling apicv flags.
> * Mock host CPU vendor in tests.
>
> Changes in v2:
> * Disable MBEC by default for machine versions < 11.0 for backwards
>   compat with older kernel and QEMU.
>
> 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. With hv_emcs, that
> feature is not used in Windows anymore. The flag is also recommended
> in the QEMU documentation [1], so start using it with a bumped
> 11.0+pve2 machine version.
>
> [0]: https://forum.proxmox.com/threads/184178
> [1]: https://www.qemu.org/docs/master/system/i386/hyperv.html#recommendations
>
> [..]

I tested this direction on my host with a AMD CPU as a smoke test and
updated the machine version from three Windows VMs from 10.1 to
11.0+pve2 (two were using i440fx and the third q35) from the web UI and
the VMs boot as expected. The windows versions were 2019, 2016, and
2022. I also tried with a Linux VM.

The code looks OK to me.

Tested-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>

-- 
Maximiliano




  parent reply	other threads:[~2026-07-15 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 10:41 [PATCH-SERIES qemu-server v3 0/4] cpu config: enable hv-evmcs for Windows 11/2022/2025 to mitigate issues with VBS Fiona Ebner
2026-07-14 10:41 ` [PATCH qemu-server v3 1/4] cpu config: disable vmx-mbec flag for machine versions < 11.0 Fiona Ebner
2026-07-14 10:41 ` [PATCH qemu-server v3 2/4] cpu config: use $version_guard rather than passing $machine_version Fiona Ebner
2026-07-14 10:41 ` [PATCH qemu-server v3 3/4] cpu config: enable hv-evmcs for Windows 11/2022/2025 to mitigate issues with VBS Fiona Ebner
2026-07-14 10:41 ` [PATCH qemu-server v3 4/4] test: cfg2cmd: allow setting host CPU vendor for a given test Fiona Ebner
2026-07-15 11:46 ` Maximiliano Sandoval [this message]
2026-07-15 12:20 ` [PATCH-SERIES qemu-server v3 0/4] cpu config: enable hv-evmcs for Windows 11/2022/2025 to mitigate issues with VBS Jonas Theisen
2026-07-15 12:42 ` applied: " Thomas Lamprecht

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=s8omrvstqzp.fsf@toolbox \
    --to=m.sandoval@proxmox.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal