Hi team
In the vCenter Server environment, I have created a Datacenter and a Cluster in which I have incorporated 5 hosts. One of these hosts contains the vCenter server. During this process, I noticed that a virtual machine called vCLS was automatically generated, but it did not power on. When analyzing the error received, the following message was displayed: "Error: Failure - Feature 'cpuid.mwait' is absent but must be present. Errors: Feature 'cpuid.mwait' is absent but must be present. Module 'FeatureCompatLate ': Failed to power on the virtual machine."
Then, upon removing all the maintenance VMs, I noticed that the VM still couldn't power on, and now the error message was: "There is no host compatible with the VM."
Could you tell me if the problem lies in the configuration of the hosts or if some additional configuration is required??
The characteristics of the hosts are the same and I describe them below:
System
BIOS Manufacturer: XFUSION BIOS
version: 8.37 Motherboard
model: CH121 V5
Processors
Model: Intel(R) Xeon(R) Gold 5220 CPU @ 2.20GHz
Processor speed: 2.2 GHz
Processor sockets: 2
Processor cores per socket: 18
Logic processors: 72
Hyperthreading: Active
I assume you might have some issues with processor or feature supporting 'cpuid.mwait'.
If the processor is latest and capable of handling 'cpuid.mwait' then I assume you might have an older BIOS. If you migrate to different host and power on, is that working?
are all of your hosts identical in hardware and firware versions?
BR
Hi denisglups
Thanks for you reply.
I have migrated the virtual machine to two of the five hosts that make up the cluster, but unfortunately, I have obtained the same result in both cases. It is important to note that, at the hardware level, all hosts are identical, however, they have differences in the firmware version. Specifically, three of them have BIOS version 8.37, while the other two have version 6.83.
BR
Did you tried to migrate the vm to hosts with diffrent BIOS? from the error message it seems that the vm is using a cpu functionality which is not supported by teh hosts it is residing. So maybe try to migrate the vm to a host where a vCLS VM is already running on.
BR
