I have a strange strange issue when a couple of my ESXi servers were powered off for a few days, when I booted them back up I couldnt get FT working across a a couple of VM's or I coulnt even use Vmotion to migrate to another host.
I have rebuilt VC and both ESXi hosts, latest versions available. The error i keep getting is a general system error occurred: Failed to initalize migration at source. Error 0xbad00a4. Vmotion failed to start due to lack of CPU or memory resources. Also getting : No Compatible host has sufficnet resources to satisfy the reservation
This error makes no sense at all, there is plenty of spare capacity on both of my ESXi hosts.
there is definitely a bug with ESXi4 , I've just installed ESX4 (full version) and I dont have any issues. Available slots is 72 (thats more like it)
yep, i think youre right.
there are a lot more bugs i think. Login via SSL and Type df -h
But do not wonder why the root partition is nearly full. Thats ESXi
Frank
Have you Open a call yet?
Or are you able to fix it by yourself?
Frank
Any update on this? I'm actually having the exact same issue. It happened after a failed attempt to enable VMware Fault Tolerance. I now have 0 slots available despite having plenty of resources available. I'm using ESX4 not ESXi and am on the latest patches.
I wasnt able to log a support call with VMware and didnt have the time to try and investigate so I rebuilt my environment with ESX4 (full version). Everything is now happy again. There is def a bug with ESXi, and some very strange business when enabling FT....
Sorry I cant be of more help, log a support call if you can with VMware.
As someone mentioned above, for me this turned out to be an Admission Control problem. Once I enabled it and set the amount of host failures then I was able to use VMotion again. VMotion was working for me before as well so I think enabling Fault Tolerance when there weren't enough slots available was what caused my issue.
Hope this helps anyone else who finds this thread.