Symptoms:
eam.log and vpxd.log of the vCenter Server: "Feature 'bad_requirement:hv.capable' was 0, but must be at least 1."eam.log:
[YYYY-MM-DDTHH:MM:SS] | ERROR | cluster-agent-2 | AuditedJob.java | 59 | JOB FAILED: [#1182617302] PowerOnVmJob(ClusterAgent(ID: 'Agent:69812e75-5135-4541-958b-23aa572487c7:null')) at com.vmware.vim.vmomi.client.http.impl.HttpExchange.invokeWithinScope(HttpExchange.java:54) ~[vlsi-client.jar:?] at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:24) ~[vlsi-client.jar:?] at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.run(HttpExchangeBase.java:51) ~[vlsi-client.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_252] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_252] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]Caused by: com.vmware.vim.binding.vim.fault.GenericVmConfigFault: Feature 'bad_requirement:hv.capable' was 0, but must be at least 1.
vpxd.log:
[YYYY-MM-DDTHH:MM:SS] info vpxd[06809] [Originator@6876 sub=Default opID=7325e956-01] [VpxLRO] -- ERROR task-88155 -- vCLS (1) -- Datacenter.ExecuteVmPowerOnLRO: vim.fault.GenericVmConfigFault:--> Result:--> (vim.fault.GenericVmConfigFault) {--> faultCause = (vmodl.MethodFault) null,--> faultMessage = (vmodl.LocalizableMessage) [--> (vmodl.LocalizableMessage) {--> key = "msg.featurecompat.requirement.number.minimumNotMet",--> arg = (vmodl.KeyAnyValue) [--> (vmodl.KeyAnyValue) {--> key = "1",--> value = "bad_requirement:hv.capable"--> },--> (vmodl.KeyAnyValue) {--> key = "2",--> value = "0"--> },--> (vmodl.KeyAnyValue) {--> key = "3",--> value = "1"--> }--> ],--> message = "Feature 'bad_requirement:hv.capable' was 0, but must be at least 1."--> },--> (vmodl.LocalizableMessage) {--> key = "msg.moduletable.powerOnFailed",--> arg = (vmodl.KeyAnyValue) [--> (vmodl.KeyAnyValue) {--> key = "1",--> value = "FeatureCompatLate"--> }--> ],--> message = "Module 'FeatureCompatLate' power on failed. "--> },--> (vmodl.LocalizableMessage) {--> key = "msg.vmx.poweron.failed",--> arg = <unset>,--> message = "Failed to start the virtual machine."--> reason = "Feature 'bad_requirement:hv.capable' was 0, but must be at least 1."--> msg = "Feature 'bad_requirement:hv.capable' was 0, but must be at least 1."
If the "vhv.enable = true" parameter is set in the /etc/vmware/config file on the ESXi host, the system attempts to enable Intel VT-x/AMD-V when the vCLS virtual machine powers on. However, the vCLS virtual machine is not compatible with Intel VT-x/AMD-V, so it fails to power on.
To resolve this issue, disable the vhv.enable setting on the ESXi host:
vi /etc/vmware/config" to open the configuration file.vhv.enable setting.Note: If hardware virtualization is required for a specific virtual machine, please enable "Hardware Virtualization" (Expose hardware assisted virtualization to the guest OS) on a per-virtual machine basis while the virtual machine is powered off.