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!
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
Problem solved. Network issue found.
what was the network issue? can you explain. cause I have same problem.
thx.
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.
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.
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.
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
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
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
also ran into this error, had duplicate IPs. same VM kernel ip on both hosts.
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.
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.
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.
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.