This issue mostly occurred when user try v-motion by vc-client in vmware vsphere6 environment there are two solution.
Try Vmotion/svmotion by using Web-Client If it failed then try this method but it is risky.
To resolve this issue, reset the CPUID Mask settings on the affected virtual machine.
To reset the CPUID Mask settings:
If the issue persists, upgrade the virtual machine's virtual hardware to the latest version.