vMotion failing at 9%: Error 0xbad010d

A short post, even though its been ages since my last post. But I promise I will fix that next¬†week. ūüôā This one is more of a personal reminder cause¬† the VMware KB had nothing on this, only this which didn’t work at all.

I was trying to vMotion a VM today (actually Redeploy VMs in vCloud but still)  and I got this error:

A general system error occured: Failed to start migration pre-copy Error 0xbad010d. The Esx host failed connect over the VMotion network.

All host were using vDS and different VLANs for Managment and vMotion vKernels.

First thing to check is vmkping vMotion IPs on the hosts, everything checked out fine.
Then I glanced over the event log on the host and I saw that the vMotion vKernel was trying to contact the mangement IP on another host, not its vMotion vKernel (which were not on the same VLAN, as they should).

Just before I had to remove the receiving host from the vDS by unassigning all pNics from its vDS, restore vSS and re-add the host to the cluster.
So the easy way to fix that is to deselect vMotion on the management vKernel on the receiving host.

Took me at least good 20 min to finally¬†check for¬†that small line in the event log ūüôā I hope this helps someone in the future so they can use the 20 min to get more coffee and bacon.

Leave a Reply

Your email address will not be published. Required fields are marked *