Re: [PATCH manager 1/1] ui: processor edit: allow setting 8 sockets

[Maximiliano Sandoval <m.sandoval@proxmox.com>]

Dominik Csapak <d.csapak@proxmox.com> writes:

> 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?

In this case it is not possible to define numa policies via --numa0,
..., --numa15 (they stop at --numa7).

When discussing this off-list with Fiona we decided to be on the safer
side, the number can be bumped again once 16 socket CPUs are more
common.

>>> 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.
>> 

-- 
Maximiliano