Error "The target host does not support the virtual machine's current hardware requirements." when Per-VM EVC Mode is enabled
Article ID: 369721
Updated On:
Products
Issue/Introduction
This issue occurs where EVC mode was previously configured on a cluster and Per-VM EVC was manually configured on certain VMs.
The configuration can be completed from the vSphere Web Client, but if Per-VM EVC is enabled on the vCenter appliance and/or the vCenter appliance is unavailable, the vmx file should be edited manually.
Symptoms:
- Per-VM EVC mode is configured in VM(s).
- Cluster-level EVC mode is not configured.
- Virtual machine reports "EVC Mode" data in vSphere Web Client.
- You cannot update the EVC mode on a virtual machine.
- vMotion fails for the virtual machine
This issue is observed in the environment where vSphere clusters in which shared datastores are typically not configured on the hosts, and where Distributed Resource Scheduler (DRS) and High Availability (HA) are not enabled.
Environment
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
VMware vCenter Server 7.x
VMware vCenter Server 8.x
Cause
This issue may occur if the virtual machine was previously configured with a CPUID mask/Per-VM EVC Mode or EVC mode was previously configured on the cluster and removed.
Warning: Unless indicated, VMware neither supports nor recommends modifying the vMotion constraints for CPU features used by applications, such as SSE3, because of the risk of application or guest operating system failure after migration.
Resolution
Manually edit the vmx file for the relevant VM to remove Per-VM EVC Mode.
- Log onto the Host UI
- Power off the VM
- Remove the VM from inventory.
- Log onto ESXi host via SSH
cd vmfs/volumes/<datastore_name>/<vm_name>cp <vm_name>.vmx <vm_name>.vmx.bkpvi <vm_name>.vmx
remove all entries for - featMask.vm.*
change the value of:
featureCompat.vm.completeMasks = "TRUE" to featureCompat.vm.completeMasks = "FALSE"- Register VM back to inventory and power on the VM.
Additional Information
Feedback
