[PATCH manager] ui: processor edit: allow setting more than 4 sockets

[PATCH manager] ui: processor edit: allow setting more than 4 sockets

[Maximiliano Sandoval]

As per our NUMA documentation [1]:

> If the NUMA option is used, it is recommended to set the number of
> sockets to the number of nodes of the host system.

Nowadays, it is common to find CPU models with 8 NUMA nodes. Two
examples are Xeon Platinum 8160 and EPYC 73F3.

The number 16 was picked to allow for some future proofing while
remaining conservative.

The schema at qemu-server does not limit the socket amount.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_numa

Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
 www/manager6/qemu/ProcessorEdit.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/manager6/qemu/ProcessorEdit.js b/www/manager6/qemu/ProcessorEdit.js
index ffaf014e..11912e3c 100644
--- a/www/manager6/qemu/ProcessorEdit.js
+++ b/www/manager6/qemu/ProcessorEdit.js
@@ -113,7 +113,7 @@ Ext.define('PVE.qemu.ProcessorInputPanel', {
             xtype: 'proxmoxintegerfield',
             name: 'sockets',
             minValue: 1,
-            maxValue: 4,
+            maxValue: 16,
             value: '1',
             fieldLabel: gettext('Sockets'),
             allowBlank: false,
-- 
2.47.3

Re: [PATCH manager] ui: processor edit: allow setting more than 4 sockets

[DERUMIER, Alexandre]

Hi,
isn't it better to extend our current numa option (which create 1 node
by socket), to something like "numa_nodes_by_socket" ?


Also, I think it could be great to enable numa by default for the vms
too.


Alexandre

-------- Message initial --------
De: Maximiliano Sandoval <m.sandoval@proxmox.com>
À: pve-devel@lists.proxmox.com
Objet: [PATCH manager] ui: processor edit: allow setting more than 4
sockets
Date: 26/03/2026 11:50:29

As per our NUMA documentation [1]:

> If the NUMA option is used, it is recommended to set the number of
> sockets to the number of nodes of the host system.

Nowadays, it is common to find CPU models with 8 NUMA nodes. Two
examples are Xeon Platinum 8160 and EPYC 73F3.

The number 16 was picked to allow for some future proofing while
remaining conservative.

The schema at qemu-server does not limit the socket amount.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_numa

Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
 www/manager6/qemu/ProcessorEdit.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/manager6/qemu/ProcessorEdit.js
b/www/manager6/qemu/ProcessorEdit.js
index ffaf014e..11912e3c 100644
--- a/www/manager6/qemu/ProcessorEdit.js
+++ b/www/manager6/qemu/ProcessorEdit.js
@@ -113,7 +113,7 @@ Ext.define('PVE.qemu.ProcessorInputPanel', {
             xtype: 'proxmoxintegerfield',
             name: 'sockets',
             minValue: 1,
-            maxValue: 4,
+            maxValue: 16,
             value: '1',
             fieldLabel: gettext('Sockets'),
             allowBlank: false,

Re: [PATCH manager] ui: processor edit: allow setting more than 4 sockets

[Maximiliano Sandoval]

"DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com> writes:

> Hi,
> isn't it better to extend our current numa option (which create 1 node
> by socket), to something like "numa_nodes_by_socket" ?

As of now, fine-tuning the NUMA configuration is achieved via the
`numa[n]` parameters.

> Also, I think it could be great to enable numa by default for the vms
> too.

I have not been able to detect any improvement when running benchmarks
on my guest with NUMA enabled with or without defining a topology. The
content of this patch is to simply reconcile the documentation and API
with the UI.

I would be interested however in setups+benchmarks that show any
improvement.

> Alexandre
>
> -------- Message initial --------
> De: Maximiliano Sandoval <m.sandoval@proxmox.com>
> À: pve-devel@lists.proxmox.com
> Objet: [PATCH manager] ui: processor edit: allow setting more than 4
> sockets
> Date: 26/03/2026 11:50:29
>
> As per our NUMA documentation [1]:
>
>> If the NUMA option is used, it is recommended to set the number of
>> sockets to the number of nodes of the host system.
>
> Nowadays, it is common to find CPU models with 8 NUMA nodes. Two
> examples are Xeon Platinum 8160 and EPYC 73F3.
>
> The number 16 was picked to allow for some future proofing while
> remaining conservative.
>
> The schema at qemu-server does not limit the socket amount.
>
> [1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_numa
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
>  www/manager6/qemu/ProcessorEdit.js | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/www/manager6/qemu/ProcessorEdit.js
> b/www/manager6/qemu/ProcessorEdit.js
> index ffaf014e..11912e3c 100644
> --- a/www/manager6/qemu/ProcessorEdit.js
> +++ b/www/manager6/qemu/ProcessorEdit.js
> @@ -113,7 +113,7 @@ Ext.define('PVE.qemu.ProcessorInputPanel', {
>              xtype: 'proxmoxintegerfield',
>              name: 'sockets',
>              minValue: 1,
> -            maxValue: 4,
> +            maxValue: 16,
>              value: '1',
>              fieldLabel: gettext('Sockets'),
>              allowBlank: false,

-- 
Maximiliano

Re: [PATCH manager] ui: processor edit: allow setting more than 4 sockets

[DERUMIER, Alexandre]

also, with memory hotplug, we allocate 1G static mem by socket
currently (QemuServer/Memory.pm)

That mean 16GB static mem for 16sockets.

I think this is be rework to have always 4GB static mem,  as unplug
under 4GB memory is not working great. I would like to rework my old
patches for virtio-mem support, but I'm very busy at work.


They are a $MAX_NUMA = 8 in Memory.pm that need to be increased.



-------- Message initial --------
De: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
À: m.sandoval@proxmox.com <m.sandoval@proxmox.com>, pve-
devel@lists.proxmox.com <pve-devel@lists.proxmox.com>
Objet: Re: [PATCH manager] ui: processor edit: allow setting more than
4 sockets
Date: 26/03/2026 14:04:35

Hi,
isn't it better to extend our current numa option (which create 1 node
by socket), to something like "numa_nodes_by_socket" ?


Also, I think it could be great to enable numa by default for the vms
too.


Alexandre

-------- Message initial --------
De: Maximiliano Sandoval <m.sandoval@proxmox.com>
À: pve-devel@lists.proxmox.com
Objet: [PATCH manager] ui: processor edit: allow setting more than 4
sockets
Date: 26/03/2026 11:50:29

As per our NUMA documentation [1]:

> If the NUMA option is used, it is recommended to set the number of
> sockets to the number of nodes of the host system.

Nowadays, it is common to find CPU models with 8 NUMA nodes. Two
examples are Xeon Platinum 8160 and EPYC 73F3.

The number 16 was picked to allow for some future proofing while
remaining conservative.

The schema at qemu-server does not limit the socket amount.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_numa

Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
 www/manager6/qemu/ProcessorEdit.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/manager6/qemu/ProcessorEdit.js
b/www/manager6/qemu/ProcessorEdit.js
index ffaf014e..11912e3c 100644
--- a/www/manager6/qemu/ProcessorEdit.js
+++ b/www/manager6/qemu/ProcessorEdit.js
@@ -113,7 +113,7 @@ Ext.define('PVE.qemu.ProcessorInputPanel', {
             xtype: 'proxmoxintegerfield',
             name: 'sockets',
             minValue: 1,
-            maxValue: 4,
+            maxValue: 16,
             value: '1',
             fieldLabel: gettext('Sockets'),
             allowBlank: false,