2V0-622 · Question #194
How does vSphere High Availability calculate the memory slot size of a virtual machine?
The correct answer is A. Virtual machine memory reservation + overhead of largest virtual machine. vSphere HA uses slot-based admission control where each slot size is determined by the most resource-intensive VM in the cluster.
Question
How does vSphere High Availability calculate the memory slot size of a virtual machine?
Options
- AVirtual machine memory reservation + overhead of largest virtual machine
- BVirtual machine memory reservation -overhead of largest virtual machine
- CVirtual machine memory reservation + overhead of smallest virtual machine
- DVirtual machine memory reservation -overhead of smallest virtual machine
How the community answered
(26 responses)- A92% (24)
- B4% (1)
- D4% (1)
Why each option
vSphere HA uses slot-based admission control where each slot size is determined by the most resource-intensive VM in the cluster.
vSphere HA calculates a memory slot size by taking the largest memory reservation among all VMs in the cluster and adding the memory overhead of that same largest VM. This ensures every slot is large enough to accommodate any VM that might need to be restarted on a failover host. The overhead accounts for VMkernel memory used for virtualization of the VM.
Subtracting overhead from the reservation would undersize the slot, meaning a slot might not hold a VM that requires both its reservation and overhead memory.
Using the overhead of the smallest VM rather than the largest would undersize slots for VMs with higher overhead, leading to incorrect admission control calculations.
Subtracting the smallest VM's overhead produces the smallest possible slot value, which would be inaccurate and allow more VMs than can actually be restarted during a failure.
Concept tested: vSphere HA slot size memory calculation
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-85D9D533-B2CD-4C4E-BD04-2F8C558F4B7E.html
Topics
Community Discussion
No community discussion yet for this question.