When using “Cluster resource percentage” for host failover capacity in vSphere HA Admission Control, the total
resource requirements are calculated from which two values? (Choose two.)
A.
Total vCPUs assigned to each VM.
B.
Average CPU usage on each VM over time.
C.
Memory reservations on each VM.
D.
Total memory assigned to each VM.
E.
Average active memory on each VM over time.
F.
CPU reservations on each VM.
Explanation:
http://www.enterprisedaddy.com/2016/10/vmware-vsphere-6-5-new-features-ha/
C,F – OK
Computing the Current Failover Capacity
The total resource requirements for the powered-on virtual machines is comprised of two components, CPU and memory. vSphere HA calculates these values.
The CPU component by summing the CPU reservations of the powered-on virtual machines. If you have not specified a CPU reservation for a virtual machine, it is assigned a default value of 32MHz (this value can be changed using the das.vmcpuminmhz advanced option.)
The memory component by summing the memory reservation (plus memory overhead) of each powered-on virtual machine.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-FAFEFEFF-56F7-4CDF-A682-FC3C62A29A95.html
5
2
CF
1
1
C,F
from :
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/vsphere/vmw-white-paper-vsphr-whats-new-6-5.pdf
vSphere HA Admission Control Improvements
Several improvements have been made to simplify the configuration of vSphere HA admission control. Starting
with vSphere 6.5, the default admission control policy is Cluster Resource Percentage. This policy calculates the
amount of failover capacity to reserve by using a percentage of the total available CPU and memory resources in
the cluster. To further simplify the configuration, this percentage is now calculated automatically by defining the
number of host failures to tolerate (FTT).
0
1
Reading same article as you, I would then say A & D
What makes you understand that this is concerned only reserver CPU and memory ?
6
0
C & F
vSphere HA calculates the CPU component by obtaining the CPU reservation of each powered-on virtual machine and selecting the largest value. If you have not specified a CPU reservation for a virtual machine, it is assigned a default value of 32MHz. You can change this value by using the das.vmcpuminmhz advanced attribute.)
vSphere HA calculates the memory component by obtaining the memory reservation, plus memory overhead, of each powered-on virtual machine and selecting the largest value. There is no default value for the
memory reservation.
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.avail.doc_50%2FGUID-85D9737E-769C-40B6-AB73-F58DA1A451F0.html
0
2
From https://pubs.vmware.com/vsphere-50/index.jsp#com.vmware.vsphere.avail.doc_50/GUID-FAFEFEFF-56F7-4CDF-A682-FC3C62A29A95.html, this is C and F
See :
The total resource requirements for the powered-on virtual machines is comprised of two components, CPU and memory. vSphere HA calculates these values.
■
The CPU component by summing the CPU reservations of the powered-on virtual machines. If you have not specified a CPU reservation for a virtual machine, it is assigned a default value of 32MHz (this value can be changed using the das.vmcpuminmhz advanced attribute.)
■
The memory component by summing the memory reservation (plus memory overhead) of each powered-on virtual machine
0
1
As weird as it sounds in the light of declared HA Admission Control improvements, VMware continues to use CPU and RAM reservations to calculate failover resource requirements. It’s safe to say that in most environments reservations are used very rarely, thus making such calculations practically meaningless. Based on this approach, all or nearly all the aggregate RAM from ESX nodes remains available for failover no matter how much of it is being used by running VMs ! This is non-sense that lives on…
0
0