damejen
asked on
Unable to migrate or vMotion any powered on VM's
Hi experts,
Come across something I've never seen in vSphere 5.0 where powered on guest machines are not able to be vMotioned or Migrated from host1 to any other host within the same Cluster. Though the other hosts 2,3,and 4 can all vMotion to each other. Migration/vMotion fails with the error. Powered off guests however are able to be migrated off to other hosts in the Cluster.
"Failed to start migration pre-copy. Error: The ESX hosts failed to connect over the VMotion network.
vMotion migration [167905794:144717226872183
Migration [167905794:144717226872183
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct."
Any ideas?
Thanks in advance
Come across something I've never seen in vSphere 5.0 where powered on guest machines are not able to be vMotioned or Migrated from host1 to any other host within the same Cluster. Though the other hosts 2,3,and 4 can all vMotion to each other. Migration/vMotion fails with the error. Powered off guests however are able to be migrated off to other hosts in the Cluster.
"Failed to start migration pre-copy. Error: The ESX hosts failed to connect over the VMotion network.
vMotion migration [167905794:144717226872183
Migration [167905794:144717226872183
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct."
Any ideas?
Thanks in advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You need to ensure, that all VMKernel Portgroups, selected as vMotion, are all on the same network.
ping and vmkping are your friendly commands to use to confirm this!
ping and vmkping are your friendly commands to use to confirm this!
ASKER
Multiple vMotion networks detected, good catch
ASKER
Thanks Andrew for the good notice of there being multiple vMotion networks. I disabled the vMotion network option on the vSwitch and it was able to vMotion without any issues.
ASKER
Nice catch, I also noticed that, from what I can see there is another VMkernel port created on each host that has that 10.2.10 network and it has both the management and vMotion options ticked in the properties of the port except for host 4 which doesn't have these options ticked.