VMware Cloud Community
Trnty
Contributor
Contributor

VMotion failed -- Failed to start migration pre-copy. Help!

ESX v4, vCenter v4 Vmotion failed with error says: A general system error occurred: Failed to start migration pre-copy. Error 0xbad003f. Connection closed by remote host, possibly due to time out.

Have anyone see this error before? Help!

Reply
0 Kudos
15 Replies
AndreTheGiant
Immortal
Immortal

Can you do vmkping between VMotion interfaces?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Trnty
Contributor
Contributor

Yes. I followed the kb document

The problem still exist after all 10 things checked.

Reply
0 Kudos
Trnty
Contributor
Contributor

Problem solved. Network issue found.

Reply
0 Kudos
tugi
Contributor
Contributor

what was the network issue? can you explain. cause I have same problem.

thx.

Reply
0 Kudos
Don_G
Contributor
Contributor

Please provide us the the network fault that caused this, i am also having the same issue and beleve it to be networking but i can ping both address.

Reply
0 Kudos
rpayne1322
Contributor
Contributor

I see this is a several months old now, but I also am curious what your resolution was as I am having the same problem. Any help you could pass along would be greatly appreciated!

Thanks.

Reply
0 Kudos
NathanEly
Contributor
Contributor

Although I was not the one with the problem originally, I had the same issue and discovered a problem with networking settings. Specifically, it was an IP conflict with the vmotion IP address and another host on the network. As soon as I fixed it, it worked immediately.

Reply
0 Kudos
VMjkasalVM
Contributor
Contributor

In case someone stumbles apon this post.

I too had the same issue only on ESX 4 (Classic). The fix for me was restarting the management services on the recieving host (Host where the VMs were migrating too.)

service mgmt-vmware restart

service vmware-vpxa restart

Reply
0 Kudos
nsolop
Expert
Expert

In mine it was also an ip address conflict.


Regards/Saludos

Por favor no olvides calificar las respuestas que te resultaron de ayuda o fueron correctas.

Please, don't forget the awarding points for "helpful" and/or "correct" answers.

________________________________________

Nicolás Solop

VMware vExpert 2010 - VCP 410- VCP 310 - VAC - VTSP

My Linkedin Profile

Join to Virtualizacion en Español group in Likedin

!http://feeds.feedburner.com/WetcomGroup.1.gif!

Reply
0 Kudos
Kopp
Contributor
Contributor

Hi all,

service mgmt-vmware restart

service vmware-vpxa restart

... on the vMotion source host (esx4.0 U1) was a solution for me.

Thx for the hint!

Regards,

JK

Reply
0 Kudos
pandaaa
Contributor
Contributor

also ran into this error, had duplicate IPs. same VM kernel ip on both hosts.

Reply
0 Kudos
Dipak
Enthusiast
Enthusiast

it happned on esxi 5.0 U1 this morning, i am not sure about IP conflict or not, but both source and Destination host's vmotion/mgmt IPs were pingable. I was not able to vmotion any live vms, however powered off VMs worked fine. I just had to restart the mgmt network, the issue appears to be gone.

Reply
0 Kudos
ryanbac123
Contributor
Contributor

I had a similar issue. The cause of the issue for me was vMotion being selected on one of my iSCSI vmkernal ports. vMotion was defaulting to that network rather then my vMotion network.

Reply
0 Kudos
pwgr
Contributor
Contributor

I ran into this issue today and the fix wasn't one listed. I have a six host cluster, set up with ip hashing on the NICs used for my iSCSI traffic. Both NICs were active on the vswitch and the vmotion kernel, but the order of the NICs, even while active, caused this issue for me. The host has been running fine for 8 months, but last night started having this issue. Swapping the NIC order, even while keeping both active, fixed the problem.

Reply
0 Kudos
din_007
Contributor
Contributor

I had the same problem. My fix was network configuration for the vMotion VMkernal where the subnet mask was incorrect. Once both host were on the correct subnet, vMotion was working as it should.

Reply
0 Kudos