100% Nux. I tried adding this as an additional field to the offering, but it was not honored.
Plus depending on the OS, the other sockets may not even be seen. As an example, Windows 10/11, I know this is a non-relistic example, but it gets the point across. If I have a VM with 16 vCPUs assigned and it spins up with 1 socket with16 cores, I am fine. But if it spins up the VM with 4 sockets, each with 4 cores, two of those sockets will not be seen by the OS because it only supports 2 sockets. From: Nux <[email protected]> Date: Thursday, December 4, 2025 at 4:18 AM To: [email protected] <[email protected]> Cc: Wei ZHOU <[email protected]> Subject: Re: Sockets to Core Ratio WARNING: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. It'd be nice to be able to set this in the compute offering as it can impact licensing of various proprietary software. I know, it's stupid, but people pay more if they have more sockets, as opposed to cores. There could be other considerations as well. Regards On 2025-12-04 07:23, Wei ZHOU wrote: > Hi, > > You can stop the vm, add a vm setting cpu.corespersocket=4, and then > start > the vm. > > > Kind regards, > Wei > > > On Thu, Dec 4, 2025 at 7:56 AM Marty Godsey <[email protected]> wrote: > >> >> Hello, >> >> >> When Cloudstack creates a VM on my XCP cluster, it always adds more >> sockets than I would like to have. So, for example, if I have a >> compute >> offering that is 4 cores, It's 2 sockets, 2 cores. Why can't it be 1 >> socket >> and 4 cores? If this is something that is not being don’t by >> Cloudstack and >> XCP, I will go that route. Any one seen this? >> >> >> Thank you everyone. >>
