A vSphere Administrator attempts to enable Fault Tolerance for a virtual machine but receives the following
error:Secondary VM could not be powered on as there are no compatible hosts that can
accommodate it.
What two options could cause this error? (Choose two.)
A.
The other ESXi host(s) are in Maintenance Mode.
B.
Hardware virtualization is not enabled on the other ESXi host(s).
C.
The other ESXi host(s) are in Quarantine Mode.
D.
Hardware MMU is enabled on the other ESXi host(s).
Explanation:
https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1008950
AB
5
0
A & B are correct.
– Enable FT on an active host. An inactive host is one that is disconnected, in maintenance mode, or in standby mode.
– FT is only supported on specific processors and BIOS settings with Hardware Virtualization (HV) enabled.
Solution: Use hosts with supported CPU models and BIOS settings.
https://kb.vmware.com/s/article/1033634
2
0
And again why not option C ?
https://blogs.vmware.com/vsphere/2016/10/whats-new-in-vsphere-6-5-host-resource-management-and-operations.html
”
Proactive HA
Proactive HA will detect hardware conditions of a host and allow you to evacuate the VMs before the issue causes an outage. Working in conjunction with participating hardware vendors, vCenter will plug into the hardware monitoring solution to receive the health status of the monitored components such as fans, memory, and power supplies. vSphere can then be configured to respond according to the failure.
Once a component is labeled unhealthy by the hardware monitoring system, vSphere will classify the host as either moderately or severely degraded depending on which component failed. vSphere will place that affected host into a new state called Quarantine Mode. In this mode, DRS will not use the host for placement decisions for new VMs unless a DRS rule could not otherwise be satisfied. Additionally, DRS will attempt to evacuate the host as long as it would not cause a performance issue. Proactive HA can also be configured to place degraded hosts into Maintenance Mode which will perform a standard virtual machine evacuation.
“
0
3
And even though this is a rather dated KB :
https://kb.vmware.com/s/article/2117771
Why not option D ?
0
1
C answer – this only limits DRS to put machines on that host, I guess
1
0
Not much to support answer D though
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-C1749AD4-70E2-406C-864C-719F54BF1BC1.html
0
0
To maintain a high level of performance and stability for your fault tolerant virtual machines and also to minimize failover rates, you should be aware of certain troubleshooting issues.
The troubleshooting topics discussed focus on problems that you might encounter when using the vSphere Fault Tolerance feature on your virtual machines. The topics also describe how to resolve problems.
You can also see the VMware knowledge base article at http://kb.vmware.com/kb/1033634 to help you troubleshoot Fault Tolerance. This article contains a list of error messages that you might encounter when you attempt to use the feature and, where applicable, advice on how to resolve each error.
Hardware Virtualization Not Enabled
You must enable Hardware Virtualization (HV) before you use vSphere Fault Tolerance.
Compatible Hosts Not Available for Secondary VM
If you power on a virtual machine with Fault Tolerance enabled and no compatible hosts are available for its Secondary VM, you might receive an error message.
Secondary VM on Overcommitted Host Degrades Performance of Primary VM
If a Primary VM appears to be executing slowly, even though its host is lightly loaded and retains idle CPU time, check the host where the Secondary VM is running to see if it is heavily loaded.
Increased Network Latency Observed in FT Virtual Machines
If your FT network is not optimally configured, you might experience latency problems with the FT VMs.
Some Hosts Are Overloaded with FT Virtual Machines
You might encounter performance problems if your cluster’s hosts have an imbalanced distribution of FT VMs.
Losing Access to FT Metadata Datastore
Access to the Fault Tolerance metadata datastore is essential for the proper functioning of an FT VM. Loss of this access can cause a variety of problems.
Turning On vSphere FT for Powered-On VM Fails
If you try to turn on vSphere Fault Tolerance for a powered-on VM, this operation can fail.
FT Virtual Machines not Placed or Evacuated by vSphere DRS
FT virtual machines in a cluster that is enabled with vSphere DRS do not function correctly if Enhanced vMotion Compatibility (EVC) is currently disabled.
Fault Tolerant Virtual Machine Failovers
A Primary or Secondary VM can fail over even though its ESXi host has not crashed. In such cases, virtual machine execution is not interrupted, but redundancy is temporarily lost. To avoid this type of failover, be aware of some of the situations when it can occur and take steps to avoid them.
1
0