Hi, all.
The target host does not support the virtual machine's current hardware requirements.
Use a cluster with enhanced vmotion compatibility (evc) enabled to create a uniform set of cpu features across the cluster, or use per-vm evc for a consistent set of cpu features for a virtual machine and allow the virtual machine to be moved to a host capable of supporting that set of cpu features. See KB 1003212 for cluster EVC information. com.vmware.vim.vmfeature.cpuid.mdclear
This could be related to a CPU feature that Intel introduced in Skylake, but removed in later CPU generations.
For details, see e.g. https://kb.vmware.com/s/article/76155
André
Thanks for your reply.
It's a feature that was introduced with Skylake, but removed again in later CPU generations. So it should basically not be used at all anymore in order to allow vMotion. From how I understand the KB, it's not exposed for VMs with either HW version less than 13, or with EVC being enabled.
CPU features are exposed to VMs at power on, so it basically depends on the ESXi build, the VM's virtual hardware version, and whether EVC is enabled, which CPU features the VM uses.
André