[pve-devel] partially-applied: [PATCH-SERIES qemu-server/manager v2 0/8] VM CPU flags: introduce vendor-agnostic 'nested-virt' CPU flag

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

On Fri, 07 Nov 2025 15:43:38 +0100, Fiona Ebner wrote:
> Changes in v2 (thanks Dano and Thomas!):
> * Pass running CPU configuration when using 'nested-virt'. This
>   ensures that migration fails early if the flag resolves differently
>   on the target.
> * Describe that live migration still only works if it's the same flag.
> * Drop adding non-existing link in API end point.
> * Keep $supported_cpu_flags private to module and add getter method.
> * Unpack @_ first at the beginning of resolve_cpu_flags().
> * ui: fix function call in the CPU flag selector widget.
> * ui: use simpler method to get all records of the store.
> * Drop already applied patches.
> 
> [...]

Applied the first three qemu-server patches already, thanks!

For the nested-flag I'm not fully sure yet if this is enough also for Windows
guests to run e.g. WSL with a non-host CPU type like x86-64-v3, which I might
not put into scope originally, but for many users it will IMO be assumed as
"has to work" if we put this in the changelog.

[1/8] critic: code style: cpu config: unpack @_ first in resolve_cpu_flags()
      commit: f505fe3ff5377286ec39329ee38b13b36bc1c940
[2/8] api: add endpoint for querying available cpu flags
      commit: d5c3d8a4c176c4fad720e6a8d410a97b28fc74a7
[3/8] cpu config: introduce is_abstracted() helper
      commit: 9eb229debbbbbb375a16c26990cb2200d6bca768


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel