With the release of vCenter 7 Update 1, VMware introduced the vCLS (vSphere Clustering Service). More information can be found here.

Error message shows failed vCLS startup due to missing CPU features.

Looking at the error details it looks like it is looking for a feature called cpuid.mwait

Error stack shows ‘FeatureCompatLate’ power on failed and ‘MWAIT’ feature absent.

Reviewing the VMX file it seems like EVC is enabled on the vCLS VMs. I didnt want to enable EVC on the whole cluster so i wanted to do it only on the specific VMs.

Doing some research i found that the VMs need to be at version 14. After upgrading the VM i was able to disable EVC on the specific VMs by following these steps:

In the vSphere Client, navigate to the virtual machine

VM details show powered off, guest OS, and usage stats.

Next we need to log in directly to the ESXi server. Under the Actions -> Upgrade VM compatibility

The image shows a list of actions related to a virtual machine in a VMware environment.

We can disable EVC on per VM level on version 14 and above, so in my case i chose ESXi 6.7U2 and clicked upgrade.

Configure VM Compatibility screen showing ESXi 6.7 U2 upgrade option.

Confirm VM Compatibility Upgrade and click yes.

Confirm VM Compatibility Upgrade. Make backup; click YES to proceed.

Next go to the Configure Tab on that VM in vCenter. Pick VMware EVC and click on Edit

The screenshot shows the VMware EVC settings in vCenter, indicating CPU mode and feature set.

Click on Yes

Warning: Editing vSphere Cluster Services may affect VM health. Click Yes to proceed.

Click on Disable EVC and Click OK

Select EVC Mode: Disable EVC, CPU Mode: Disable, OK button.

The next time it tries to power on the VM, the system will automatically set the proper EVC CPU Mode and it should power on.

Power On virtual machine step shows “Completed” status.

Once the first VM starts up it will most likely deploy a few additional ones, follow the same steps as above again on the new VMs