cpu topology assigned at power on for VCSA ?

[mpac]

With virtual hardware 20 we can set the vcpu assignment to 'Assigned at power on' The question is how can i apply this setting to the VCSA because the vm must be in powered off state and i cannot find this option in the ESXi gui ?

-------------------------------------------

[Daniel Bonner]

For vSphere 8 and later, CPU topology on a vCenter Server Appliance (VCSA) is assigned at power on automatically by default, meaning the ESXi host decides the best distribution of virtual CPUs (vCPUs). This "Assigned at power on" setting, found in the VM's settings under the CPU section, allows the host to automatically set the "Cores per Socket" and NUMA node configurations to best match the underlying physical hardware. You can change this to a manual configuration but are warned that it may impact performance. Office ally

-------------------------------------------

[CSpreha]

Since VCSA are deployed as VMX10, it will not have that option, and BCM does not support changing that hardware version, the point is moot.  I know some people do, I'm well aware things keep working, but their official stance has never changed that you're not SUPPOSED to change it on appliances.  Considering VMX10 is not even protected from side-channel and other vulns (min VMX11), it would be nice to see BCM update their appliance-vmx upgrade policies.

-------------------------------------------

[ninjabrum]

This is the recommendation for just about any virtual appliance provider (Cisco, VMware, etc).  The only supported method to change the hardware compatibility is to install a new appliance. It's like swapping motherboards and expecting everything to still work.  Windows is forgiving in this aspect, locked down *nix or Photon appliances are not.  See the first point under this KB that references VCSA.  If things so sideways and support sees VCSA at a different hardware version, they may refuse to troubleshoot and will direct you to revert to a backup or redeploy. Don't mess with hardware versions without a very valid and supported reason for doing so.

https://knowledge.broadcom.com/external/article/315390/upgrading-a-virtual-machine-to-the-lates.html

-------------------------------------------