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 v4 12/17] ui: add basic custom CPU model editor
Date: Mon, 11 May 2026 15:52:37 +0200 [thread overview]
Message-ID: <xbgfabc44uhme7jnccjiadi7yb4ah3eiulu33x6fcaefgxicbt@qumrkqcwdjjn> (raw)
In-Reply-To: <77381399-e915-4b5f-a5e4-2e3ea4bcd9a5@proxmox.com>
On Mon, May 11, 2026 at 11:27:06AM +0200, Fiona Ebner wrote:
> Am 30.04.26 um 6:00 PM schrieb Arthur Bied-Charreton:
> > diff --git a/www/manager6/dc/CPUTypeEdit.js b/www/manager6/dc/CPUTypeEdit.js
> > new file mode 100644
> > index 00000000..594772ed
> > --- /dev/null
> > +++ b/www/manager6/dc/CPUTypeEdit.js
> > + items: [
> > + {
> > + xtype: 'inputpanel',
> > + onGetValues: function (values) {
> > + let win = this.up('window');
> > +
> > + PVE.Utils.delete_if_default(values, 'reported-model', '', win.isCreate);
> > + PVE.Utils.delete_if_default(values, 'hv-vendor-id', '', win.isCreate);
> > + PVE.Utils.delete_if_default(values, 'phys-bits', '', win.isCreate);
> > + PVE.Utils.delete_if_default(values, 'flags', '', win.isCreate);
>
> Should we also do this for the 'hidden' property?
>
Yea, would make sense, will add it
> > +
> > + if (win.isCreate) {
> > + delete values.delete;
> > + }
> > +
> > + return values;
> > + },
> > + column1: [
> > + {
> > + xtype: 'pmxDisplayEditField',
> > + fieldLabel: gettext('Name'),
> > + cbind: {
> > + editable: '{isCreate}',
> > + value: '{cputype}',
> > + },
> > + name: 'cputype',
> > + renderer: (val) => val.replace(/^custom-/, ''),
> > + allowBlank: false,
> > + },
> > + {
> > + xtype: 'CPUModelSelector',
> > + fieldLabel: gettext('Base Model'),
> > + showCustomModels: false,
> > + name: 'reported-model',
> > + autoEl: {
> > + tag: 'div',
> > + 'data-qtip': gettext(
> > + 'CPU model the rest of the configuration will be based on.',
>
> Nit: s/will be/is/
> This in particular makes it sound slightly more correct when editing and
> we can still use the same gettext for the grid below.
>
> Since the historic (back-end) default is the non-recommended kvm64
> model, I think we should have the user make an actual choice here and
> disallow empty for the model selector field. At least in the isCreate
> case, otherwise I guess we need to keep it working for compat with
> pre-existing manually created custom models.
>
Alright, makes sense, will add in v5 - thanks for the context!
> > diff --git a/www/manager6/dc/CPUTypeView.js b/www/manager6/dc/CPUTypeView.js
> > new file mode 100644
> > index 00000000..207673a7
> > --- /dev/null
> > +++ b/www/manager6/dc/CPUTypeView.js
> > + {
> > + header: gettext('Base Model'),
> > + flex: 1,
> > + dataIndex: 'reported-model',
> > + autoEl: {
> > + tag: 'div',
> > + 'data-qtip': gettext('CPU model the rest of the configuration will be based on.'),
>
> Nit: s/will be/is/
>
ack
> > + },
> > + },
> > + {
> > + header: gettext('Phys-Bits'),
> > + flex: 1,
> > + dataIndex: 'phys-bits',
> > + },
> > + {
> > + header: gettext('Hidden'),
> > + flex: 1,
> > + dataIndex: 'hidden',
> > + },
> > + {
> > + header: gettext('HyperV-Vendor'),
> > + flex: 1,
> > + dataIndex: 'hv-vendor-id',
> > + },
> > + {
> > + header: gettext('Flags'),
> > + flex: 2,
> > + dataIndex: 'flags',
> > + },
> > + ],
> > +
> > + tbar: [
> > + {
> > + text: gettext('Add'),
> > + handler: 'onAdd',
> > + },
> > + '-',
> > + {
> > + xtype: 'proxmoxStdRemoveButton',
> > + baseurl: '/api2/extjs/cluster/qemu/custom-cpu-models/',
> > + getRecordName: (rec) => rec.data.cputype,
> > + getUrl: function (rec) {
> > + let me = this;
> > + return me.baseurl + rec.data.cputype;
> > + },
> > + confirmMsg: function (rec) {
> > + return Ext.String.format(
> > + gettext('Are you sure you want to remove the custom CPU model {0}'),
> > + `"${rec.data.cputype.replace(/^custom-/, '')}"?`,
>
> The question mark should be part of the template string
>
ack
> > diff --git a/www/manager6/form/PhysBitsSelector.js b/www/manager6/form/PhysBitsSelector.js
> > new file mode 100644
> > index 00000000..78f932a6
> > --- /dev/null
> > +++ b/www/manager6/form/PhysBitsSelector.js
> > + items: [
> > + {
> > + xtype: 'radiofield',
> > + boxLabel: gettext('Default'),
> > + inputValue: 'default',
> > + checked: true,
> > + reference: 'modeDefault',
> > + listeners: {
> > + change: 'onRadioChange',
> > + },
> > + isFormField: false,
> > + },
> > + {
> > + xtype: 'radiofield',
> > + boxLabel: gettext('Host'),
> > + inputValue: 'host',
> > + reference: 'modeHost',
> > + listeners: {
> > + change: 'onRadioChange',
> > + },
> > + isFormField: false,
> > + },
> > + {
> > + xtype: 'fieldcontainer',
> > + layout: 'hbox',
> > + items: [
> > + {
> > + xtype: 'radiofield',
> > + boxLabel: gettext('Custom'),
> > + inputValue: 'custom',
> > + listeners: {
> > + change: 'onRadioChange',
> > + },
> > + reference: 'modeCustom',
> > + isFormField: false,
> > + },
>
> I feel like we could be a bit more descriptive here, maybe:
> Default from QEMU
> Inherit from host CPU
> Custom number
> ?
>
Sounds good! Will add in v5
> > + {
> > + xtype: 'numberfield',
> > + width: 60,
> > + margin: '0 0 0 10px',
> > + minValue: 8,
> > + maxValue: 64,
> > + reference: 'customNum',
> > + allowBlank: false,
> > + isFormField: false,
> > + disabled: true,
> > + },
> > + ],
> > + },
> > + ],
> > +});
>
next prev parent reply other threads:[~2026-05-11 13:53 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 16:00 [PATCH docs/manager/qemu-server v4 00/17] Add API and UI for custom CPU models Arthur Bied-Charreton
2026-04-30 16:00 ` [PATCH pve-docs v4 01/17] qm: add anchor to "CPU Type" section Arthur Bied-Charreton
2026-05-07 10:34 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 02/17] cpu config: rename CPU models config path variable Arthur Bied-Charreton
2026-05-07 10:57 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 03/17] cpu flags: move cpu flags-related utilities to their own module Arthur Bied-Charreton
2026-05-07 11:15 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 04/17] cpu flags: add helper querying CPU flags with nodes supporting them Arthur Bied-Charreton
2026-05-07 11:57 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 05/17] cpu config: add helpers to lock and write config Arthur Bied-Charreton
2026-05-07 12:06 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 06/17] cpu: register standard option for CPU format Arthur Bied-Charreton
2026-05-07 12:11 ` Fiona Ebner
2026-05-07 14:01 ` Arthur Bied-Charreton
2026-05-07 14:08 ` Fiona Ebner
2026-05-08 6:40 ` Arthur Bied-Charreton
2026-04-30 16:00 ` [PATCH qemu-server v4 07/17] cpu config: set 'type' field before writing Arthur Bied-Charreton
2026-05-07 12:24 ` Fiona Ebner
2026-05-08 7:48 ` Arthur Bied-Charreton
2026-04-30 16:01 ` [PATCH qemu-server v4 08/17] cpu flags: improve flags list returned by endpoint Arthur Bied-Charreton
2026-05-07 13:10 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 09/17] api: add endpoint querying available CPU flags cluster-wide Arthur Bied-Charreton
2026-05-07 13:29 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 10/17] api: add CRUD handlers for custom CPU models Arthur Bied-Charreton
2026-05-07 14:02 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 11/17] ui: cpu model selector: allow filtering out custom models Arthur Bied-Charreton
2026-05-11 8:53 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 12/17] ui: add basic custom CPU model editor Arthur Bied-Charreton
2026-05-11 9:27 ` Fiona Ebner
2026-05-11 13:52 ` Arthur Bied-Charreton [this message]
2026-04-30 16:01 ` [PATCH pve-manager v4 13/17] ui: cpu flags selector: add CPU flag editor for custom models Arthur Bied-Charreton
2026-05-11 11:35 ` Fiona Ebner
2026-05-11 14:14 ` Arthur Bied-Charreton
2026-04-30 16:01 ` [PATCH pve-manager v4 14/17] ui: cpu flags selector: fix buffered rendering error Arthur Bied-Charreton
2026-05-11 13:36 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 15/17] ui: cpu flags selector: allow filtering out flags supported on 0 nodes Arthur Bied-Charreton
2026-05-11 13:40 ` Fiona Ebner
2026-05-11 13:42 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 16/17] ui: cpu flags selector: add search bar for large lists of flags Arthur Bied-Charreton
2026-05-11 13:56 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 17/17] RFC: ui: group custom CPU with resource mappings Arthur Bied-Charreton
2026-05-11 14:01 ` Fiona Ebner
2026-05-06 14:31 ` [PATCH docs/manager/qemu-server v4 00/17] Add API and UI for custom CPU models David Riley
2026-05-07 7:14 ` Arthur Bied-Charreton
2026-05-11 10:42 ` Fiona Ebner
2026-05-11 14:16 ` Arthur Bied-Charreton
2026-05-12 8:11 ` Arthur Bied-Charreton
2026-05-12 8:50 ` Fiona Ebner
2026-05-12 9:00 ` Arthur Bied-Charreton
2026-05-11 14:08 ` Fiona Ebner
2026-05-11 14:21 ` Arthur Bied-Charreton
2026-05-15 9:30 ` superseded: " 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=xbgfabc44uhme7jnccjiadi7yb4ah3eiulu33x6fcaefgxicbt@qumrkqcwdjjn \
--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 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.