2V0-620 · Question #11
An ESXi 6.x host consists of 24 logical cores. Hyperthreading is enabled on the host. What is the maximum number of vCPUs that can be assigned to a virtual machine on this host?
The correct answer is A. 24. In vSphere, the maximum number of vCPUs assignable to a single VM is bounded by the number of physical processor cores on the host, which is 24 regardless of hyperthreading doubling the logical processor count.
Question
An ESXi 6.x host consists of 24 logical cores. Hyperthreading is enabled on the host. What is the maximum number of vCPUs that can be assigned to a virtual machine on this host?
Options
- A24
- B48
- C64
- D128
How the community answered
(40 responses)- A93% (37)
- C5% (2)
- D3% (1)
Why each option
In vSphere, the maximum number of vCPUs assignable to a single VM is bounded by the number of physical processor cores on the host, which is 24 regardless of hyperthreading doubling the logical processor count.
VMware limits the maximum vCPUs per VM to the number of physical cores available on the ESXi host; with 24 physical cores, the binding maximum is 24 vCPUs. Hyperthreading presents 48 logical processors to the OS but does not increase the physical core count, which remains the scheduling constraint governing the maximum vCPU assignment for any single virtual machine.
48 equals the number of logical processors after hyperthreading (24 physical cores x 2 threads per core), but VMware's maximum vCPU limit per VM is governed by physical core count, not the hyperthreaded logical processor count.
64 exceeds both the physical core count (24) and the hyperthreaded logical processor count (48) on this host, making it an invalid vCPU assignment.
128 is the absolute per-VM vCPU configuration ceiling in vSphere 6.x, but it is unachievable on this host because the physical core count of 24 is the binding per-host constraint.
Concept tested: Maximum vCPUs per VM bounded by host physical core count
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-789C3913-1053-4850-A0F0-E29C3D32B6DA.html
Topics
Community Discussion
No community discussion yet for this question.