Well the error message kinda does give it away, it seems your hosts are unable to connect. vmotion cancelling at 10 or 14% would be my guess?
- There are a few things to check. For a classic vmotion both hosts (source and destination) need to see the same SAN. Is that the case?
- Did you configure a vmotion interface for both the source and destination host in the same subnet? => routed vmotion is not supported
- If yes is that traffic passed through the same subnet as other vmkernel traffic (NFS; iSCSI) => multi homing is not supported in ESXi
- In the host > configuration > networking tab you should be able to see which vmkernel port is used/configured for vmotion on the source and destination, you can try pinging the 2 devices from each other via "vmkping -I vmk0 -d -s MTUSIZE xxx.xxx.xxx.xxx" (more information can be found at http://kb.vmware.com/kb/1003728)
- You can use tcpdump-uw on both hosts to see if the outgoing packets are actually being received on the target (http://kb.vmware.com/kb/1031186)
- And the general vmotion stalls before it can connect to the target host kb (http://kb.vmware.com/kb/1003734)
This is some network configuration error which usually is caused by either firewall isssues or network design.
