I have installed Virtual Center 2.5 and ESX 3.5, everythings works fine, but suddenly Vmotion stopped running. In some VM's I can not migrate them. It starts migrating untill 10% and then fails. I have checked reserverved memory/CPU but the error continues.
Any help would be appreciated
Configure the network again, remove the kernel. Click ok to SAVE. Then add the kernel again, using the same settings.
Ping from an external machine,and verify you can ping the vmkernel IP, then you should be fine.
From your VI console -> Click on host name -> configuration tab -> networking. Click properties on the switch with vmotion, and remove the vmkernel from the switch.
Sorry, I didn't mean reconfigure your host, just the switch.
I have the same problem, I tried to remove and rejoin the VMkernel vswitch. But it didn't work, i got the error message: A specified parameter was not correct. Vim.Host.VirtualNic.Specification.Ip
What could that be?
Yes, I mean VmWare Converter Agent. My problem was:
When converter started to importing physical machine it stopped at 2% and then it shows me the error Bad0007.Bad Parameter.....This situation was resolved by unistalling / installing the converter Agent on my Virtual Machine.
I had this same error when i tried to Vmotion some guests. Vmotion was working fine for me but it suddenly stopped. One thing is i was trying to vmotion from a ESX 3.01 to a ESX 3.5. but that shouldnt have made a difference.
The fix was to remove the Vmotion VMKernel and and then re-add it to both source and target hosts. This fixed it for me.
Same problem here, It appeared something else was using my VMotion IP addresses. Changed them to troubleshoot and it worked again.
The thing that made it harder to troubheshoot is that a vmkping obviously worked, didn't knew it was going to another device though
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!
In my case I was using the same IP address for two VMotion PortGroups on two different ESX hosts.
VC should check for already used IP's. I think it would be easy to implement and useful (there's always human errors, with or without ITIL :P)
I recently had the same error message at a customer site running ESX 3.5U3 on HP cClass 460c Blades using HPs Virtual Connect. When doing a Live migration I would only get approx 60% success with VMotions, and especially low success 15% with VMs that have more than 4GB of ram.
The suggested fixes at kb.vmware.com 1007982 did not make any difference. VMotions would still fail on a regular basis with the migrate timeout settings increased.
What did seem to resolve the fix was updating the ESX hosts to Update 4 and the patches listed in the kb article 1009250.
I hope this will help some others out there with a similar config. I believe it was probably due to the BNX2 Broadcom driver updates that resolved it.
Unfortunetly ive experience this error for vmotions on ESX3.5U4. Most of the time i can see from vmkwarning that it cannot connect to the destination host vmotion ip, however i can vmkping from source to destination. Painful work around has been to disable and re-enable vmotion on source and destinataion