Link to home
Start Free TrialLog in
Avatar of saravanan_sj
saravanan_sj

asked on

Virtual processor per VM

I need to increase a virtual cpu from 2 to 3 per virtual machine in ESX 3.5 (we have enough CPUs)
Would like to know the recommendation and will it be any problem if I assign 3 CPUs per VM
Avatar of coolsport00
coolsport00
Flag of United States of America image

Usually only need 1 vCPU, but can certainly increase it if OS and/or apps require more in sys req's or you notice performance issues.

~coolsporr00
Avatar of saravanan_sj
saravanan_sj

ASKER

It is a known issue in Virtual Machine Manager 2008 R2 that if you select 3 Virtual CPU (Processors) for a Virtual Machine in Hyper-v, the VMM Administrator Console will crash and terminate immediately when you try to view the properties of that Virtual Machine.

the above is for Hyper-V

is there any issue as above in ESX 3.5?
Avatar of Miguel Angel Perez Muñoz
Maybe HAL of virtualized machine not support the change. What operating systems has virtualized?
it is windows server 2003 R2 Standard
first would like to confirm , is this possible to assign 3 VCPUs per VM in ESX 3.5?
i would need to confirm the above question, bit urgent.

can someone help me
According to: http://en.m.wikipedia.org/wiki/Windows_Server_2003, the OS can support up to 4 CPUs. There is no issue within the hypervisor. But regardless, making any hardware chg could corrupt your VM, so make a backup before the chg (thats best practice, anyway).

~coolsport00
And, you're limited to 4 vCPUs per VM per the Config Max Guide:
http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_config_max.pdf

~coolsport00
The max configuration and support of CPU is 4 in ESX 3.5, but my doubt was will we able to set 3 VCPU for VMs in ESX 3.5

I got the answer for my question , that is we will not be able to set 3 VCPUs for a VMs created in ESX 3.5
You can, but my question is why are you needing to implement so many vCPUs for VMs, unless specs for the apps running on those VMs require several vCPUs? Typically, 1 vCPU per VM is all that is required. Adding more, outside of system or app specifications can lead to CPU contention, and thus cause latency & poor performance for a VM (you can read more about vCPU allocation in the Res Mgmt Guide). Just to clarify, CPU allocation is not a "1 to 1" resource allocation as it is with RAM. You can typically have 4-5 VMs running off 1 physical CPU *core* (not phys CPU socket). The max number of sockets & cores is typically how many vCPUs you're allowed to give a VM, limited only by the hypervisor version (3.x vs 4.x) as well as the licensing version (Adv vs. Ent Plus, etc.).

Hope that helps.

Regards,
~coolsport00
ASKER CERTIFIED SOLUTION
Avatar of saravanan_sj
saravanan_sj

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This answer is the correct solution for this question