From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-manager 5/8] ui: Add CPU flag editor for custom models
Date: Fri, 27 Mar 2026 10:34:06 +0100 [thread overview]
Message-ID: <l5kt54g6bkttw4x6kis4lxhwm7jaylfsbmdltuju3x4lbwpxn6@kd5mddchetzg> (raw)
In-Reply-To: <8197fbbc-9642-49c0-8a5e-b5ce7208cbba@proxmox.com>
On Thu, Mar 26, 2026 at 04:22:24PM +0100, Fiona Ebner wrote:
> Am 12.03.26 um 9:40 AM schrieb Arthur Bied-Charreton:
> > Add CPU flag editor to the CPUTypeEdit component, using the VMCPUFlagSelector
> > also used in the VM creation flow. By default, only show the CPU flags that
> > are currently meant to be shown in the VM creation window, see [0]. When in
>
> In the VM Hardware/creation window, I think we should not allow
> selecting the accelerator for the flags by the user, but use the
> accelerator that the VM currently has configured. With a
> hint/description that this is the currently configured one.
>
Good idea, I will add a `kvm` config property to VMCPUFlagSelector so we
can differentiate and show the hint.
> Nice work so far from both you and the original author!
Thanks :)
>
> > CPUTypeEdit, show all available flags.
> >
> > For each flag in VMCPUFlagSelector, also display which node(s) it is available
> > on to limit misconfigurations.
> >
>
> ---snip 8<---
>
> > diff --git a/www/manager6/form/VMCPUFlagSelector.js b/www/manager6/form/VMCPUFlagSelector.js
> > index 74b1a2c4..06c9d9f1 100644
> > --- a/www/manager6/form/VMCPUFlagSelector.js
> > +++ b/www/manager6/form/VMCPUFlagSelector.js
> > @@ -1,3 +1,19 @@
> > +const VM_CPU_FLAGS_SUBSET = {
> > + aes: true,
> > + 'amd-no-ssb': true,
> > + 'amd-ssbd': true,
> > + 'hv-evmcs': true,
> > + 'hv-tlbflush': true,
> > + ibpb: true,
> > + 'md-clear': true,
> > + 'nested-virt': true,
> > + pcid: true,
> > + pdpe1gb: true,
> > + 'spec-ctrl': true,
> > + ssbd: true,
> > + 'virt-ssbd': true,
>
> I'd rather not have the list hard-coded here if it can be avoided and
> from what we discussed for the qemu-server patches I think it won't be
> needed anymore, right?
Yea this is ugly & already dropped from v2, I moved everything to the
backend when addressing your feedback for the cpu-flags endpoint :)
next prev parent reply other threads:[~2026-03-27 9:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 8:40 [PATCH manager/qemu-server 0/8] Add API and UI for custom CPU models Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH pve-manager 1/8] ui: VMCPUFlagSelector: Fix unknownFlags behaviour Arthur Bied-Charreton
2026-03-25 15:57 ` Fiona Ebner
2026-03-26 13:47 ` Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH pve-manager 2/8] ui: CPUModelSelector: Fix dirty state on default Arthur Bied-Charreton
2026-03-26 9:53 ` Fiona Ebner
2026-03-26 14:14 ` Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH pve-manager 3/8] ui: CPUModelSelector: Allow filtering out custom models Arthur Bied-Charreton
2026-03-26 9:59 ` Fiona Ebner
2026-03-26 14:17 ` Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH pve-manager 4/8] ui: Add basic custom CPU model editor Arthur Bied-Charreton
2026-03-26 15:10 ` Fiona Ebner
2026-03-27 9:23 ` Arthur Bied-Charreton
2026-03-27 9:32 ` Fiona Ebner
2026-03-27 9:34 ` Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH pve-manager 5/8] ui: Add CPU flag editor for custom models Arthur Bied-Charreton
2026-03-26 15:22 ` Fiona Ebner
2026-03-27 9:34 ` Arthur Bied-Charreton [this message]
2026-03-26 15:40 ` Maximiliano Sandoval
2026-03-27 7:48 ` Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH qemu-server 6/8] qemu: Add helpers for new custom models endpoints Arthur Bied-Charreton
2026-03-20 17:20 ` Fiona Ebner
2026-03-23 6:56 ` Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH qemu-server 7/8] api: qemu: Extend cpu-flags endpoint to return actually supported flags Arthur Bied-Charreton
2026-03-20 17:20 ` Fiona Ebner
2026-03-23 7:25 ` Arthur Bied-Charreton
2026-03-12 8:40 ` [PATCH qemu-server 8/8] api: qemu: Add CRUD handlers for custom CPU models Arthur Bied-Charreton
2026-03-23 14:46 ` Fiona Ebner
2026-03-23 16:04 ` Arthur Bied-Charreton
2026-03-23 16:10 ` Arthur Bied-Charreton
2026-03-24 9:27 ` Fiona Ebner
2026-03-26 14:54 ` [PATCH manager/qemu-server 0/8] Add API and UI " Fiona Ebner
2026-03-27 13:07 ` Arthur Bied-Charreton
2026-03-27 13:28 ` 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=l5kt54g6bkttw4x6kis4lxhwm7jaylfsbmdltuju3x4lbwpxn6@kd5mddchetzg \
--to=a.bied-charreton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox