I have about a dozen VMs that fail at 20% when trying to vmotion. VMware Tools is up to date. I have three hosts in a cluster and the problem is not specific to any one host. I have cloned these VMs and the issues persists on the clones suggesting the problem is with a VM config or possibly within the guest OS. Most of the VMs on these host are not experiencing any issues during vmotion. The physical network is good.
vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion networksettings and physical network configuration.
The physical network connections are good. As I stated the majority of VMs will migrate with no issues, to and from the same hosts using the same network. If this was a physical network issue, I would not have consistent failures with specific VMs. At least I dont see how it could be the physical network in this situation.
We are getting the same problem, some VMs can be VMotioned and other VMs cannot be VMotioned (same source host & same destination host in both cases). Please did you find a solution?
How many NIC's confirmed for the vmotion? can you keep one nic in unused state and try vmotion and check if that works.. repeat the same for other nic to verify if they both are working.. I suspect one of them had some configuration issues to the physical ...
I’ve run into this before with a MTU mismatch over some links in the data path. some of the LACP connections between TOR and Aggergation would be right and one would be at 1500 MTU.
I’ve also seen a failed backup job keep a VM from migrating but that is pretty rare.
