From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com,
Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Subject: applied: [PATCH qemu-server 1/3] cpu flags: include Hyper-V enlightenment flags in supported flags
Date: Tue, 26 May 2026 10:43:01 +0200 [thread overview]
Message-ID: <177978495657.52909.9447298169275857943.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260522132122.712794-2-a.bied-charreton@proxmox.com>
On Fri, 22 May 2026 15:21:20 +0200, Arthur Bied-Charreton wrote:
> QEMU advertises the Hyper-V enlightenment flags [0] through a different
> CPUID range, which query-cpu-model-expansion does not cover by default.
>
> This leads to query_supported_cpu_flags reporting the hv-* flags as
> unsupported [1] even though some of them are in the VM-specific flags
> and QEMU would accept them when starting a VM.
Applied, thanks!
[1/3] cpu flags: include Hyper-V enlightenment flags in supported flags
commit: 698550c2682ed8ab20c3d41a56be79b11063c05a
next prev parent reply other threads:[~2026-05-26 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 13:21 [PATCH qemu/qemu-server 0/3] include Hyper-V enlightenment flags in CPU flags lists Arthur Bied-Charreton
2026-05-22 13:21 ` [PATCH qemu-server 1/3] cpu flags: include Hyper-V enlightenment flags in supported flags Arthur Bied-Charreton
2026-05-26 8:43 ` Fiona Ebner [this message]
2026-05-22 13:21 ` [PATCH pve-qemu 2/3] build: query Hyper-V enlightenment flags for CPU flags list Arthur Bied-Charreton
2026-05-28 13:38 ` Fiona Ebner
2026-05-28 15:30 ` Arthur Bied-Charreton
2026-05-28 15:43 ` Fiona Ebner
2026-05-29 5:53 ` Arthur Bied-Charreton
2026-05-22 13:21 ` [PATCH pve-qemu 3/3] build: fail when recognized CPU flags list changes 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=177978495657.52909.9447298169275857943.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=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 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.