public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager 1/1] ui: processor edit: allow setting 8 sockets
Date: Fri, 10 Jul 2026 09:44:18 +0200	[thread overview]
Message-ID: <bfdc0b90-8209-4ba5-b745-c6ac074539d2@proxmox.com> (raw)
In-Reply-To: <s8ojyr3cmu1.fsf@toolbox>



On 7/10/26 9:42 AM, Maximiliano Sandoval wrote:
> Dominik Csapak <d.csapak@proxmox.com> writes:
> 
>> if the backend does not have an upper limit, shouldn't we use the same
>> behavior in the frontend?
> 
> We have a hardcoded limit of $MAX_NUMA = 8 in qemu-server's Memory.pm as
> mentioned by Alexandre in a reply to v1. I opted to be on the safer side
> without redoing the entire numa handling.
> 
> At the moment there are systems with 8 sockets and at least one customer
> asked for this in enterprise support.
> 

but this is only tangentially related to the socket amount?

i can boot a vm with e.g. 16 sockets + numa 1 boot perfectly fine?

>> AFAICS two issues arise by having a lower value here than the backend:
>> * we have to raise this (probably) again in the future
>> * a config with a higher value cannot be edited in the gui
>>    (because it get's invalid)
>>
>> So i'd prefer just to remove the maxValue here completely.
>>
>> If there is any detrimental effect when having to much sockets
>> configured, we could add a warning e.g. when the sockets
>> is > 8.
> 





  reply	other threads:[~2026-07-10  7:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 11:47 [PATCH manager 1/1] ui: processor edit: allow setting 8 sockets Maximiliano Sandoval
2026-07-06 11:47 ` Maximiliano Sandoval
2026-07-09 14:30 ` Dominik Csapak
2026-07-10  7:42   ` Maximiliano Sandoval
2026-07-10  7:44     ` Dominik Csapak [this message]
2026-07-10  7:46       ` Dominik Csapak
2026-07-10  8:07       ` Maximiliano Sandoval
2026-07-10  8:19         ` Dominik Csapak
2026-07-10  8:44           ` superseded: " 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=bfdc0b90-8209-4ba5-b745-c6ac074539d2@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal