Heavy over committed host and storage/network with high latency can be some issues that can cause vMotion failure, take a look at this KB article for detailed information: VMware KB: vMotion fails with the error: Migration to host <> failed with error
If there are multiple vmkernel ports in the same network, the ESX/ESXi host may not use the vmkernel port checked off for vMotion when using the vmkping command. The host uses the vmkernel port associated with that IP subnet in its routing/forwarding table. If there is a physical switch configuration problem, vmkping may show connectivity as working correctly, but the actual vmkernel port associated with vMotion may not have access to that IP network on the physical network.
This issue occurs if there are two vmx-swap files present in the virtual machine directory. The directory should contain one standard ESXi vswp file (vmname.vswp) and one VMX-swap file (vmx-vmname.vswp) for vmx memory overhead.
This issue occurs because there are missing cpuid values in the .vmx file located on the virtual machine being vMotioned.
Below are the kb article with the resolution.
Kindly mark this as correct or helpful if this answers your query.