From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager 1/1] ui: processor edit: allow setting 8 sockets
Date: Mon, 6 Jul 2026 13:47:11 +0200 [thread overview]
Message-ID: <20260706114719.340123-1-m.sandoval@proxmox.com> (raw)
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 schema at qemu-server does not limit the socket amount. However, $MAX_NUMA
is hard-coded to 8 at qemu-server's Memory.pm , so we bump it to 8 to be on the
safe side.
[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_numa
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
Notes:
Differences from v1:
- Set the maxValue to 8
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 719f771a7..1afc1fd78 100644
--- a/www/manager6/qemu/ProcessorEdit.js
+++ b/www/manager6/qemu/ProcessorEdit.js
@@ -129,7 +129,7 @@ Ext.define('PVE.qemu.ProcessorInputPanel', {
xtype: 'proxmoxintegerfield',
name: 'sockets',
minValue: 1,
- maxValue: 4,
+ maxValue: 8,
value: '1',
fieldLabel: gettext('Sockets'),
allowBlank: false,
--
2.47.3
next reply other threads:[~2026-07-06 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 11:47 Maximiliano Sandoval [this message]
2026-07-06 11:47 ` [PATCH manager 1/1] ui: processor edit: allow setting 8 sockets Maximiliano Sandoval
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=20260706114719.340123-1-m.sandoval@proxmox.com \
--to=m.sandoval@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