vCPU assigmenment

[BhagwanSinghJai]

I have a  Server with 2 processor with 12 Cores, and one Virtual Installed with Windows Server 2008 R2 Enterprise Edition, Total available physical cores are 24, I want to aasign at lest 16 cores to this machine pls. suggest configuration for the same

[mprazeres183]

Hi BhagwanSinghJai

I just created a vGuest on my end.
So what you need to do is first the vGuest needs to be off, otherwise you can't change the CORES section.
Then you select the amount of CPUs

So you have 2 options:

Option one select 24 CPUs as you have 24 installed, then select 12 Cores, this will give you 2 Sockets. Or it will use from the 2 CPUs in your Host 12 Cores per Socket, so it will give you the 24.

But this maight now be enough, as you wanted 16.

So you have to go for this Option.
You need to use 16 CPUs and use 16 Cores per Socket. The issue here is, it will only use one of your installed CPUs but that's not a problem "normally".

This will be your best choice.

Best regards,

Marco

[Dave_the_Wave]

NUMA will take care of your sockets/cores/threads, if the choice OS doesn't have any socket handicaps, 1Socket=1CPU=1core makes for easy setup. From all the tests I have done, the vm only cares about the total final count of beer cans you gave it, regardless of if they were bundled in four 6 packs, or two 12 packs, or the one 24 flat.

vmware documentation obfuscated the matter somewhat with Windows OS licensing issues. Some Standard Server versions will only allow maximum 2way=2sockets, so if that was the only Win lincense you had, you could ramp up an beefy vm by setting it up as 2 CPU with 8 cores per socket. Now you have a Windows Standard Server that is running 16 threads that would be otherwise impossible in the real world.