Insufficient resources to satisfy HA failover level

[prutter]

Getting this error from a VM that was just Cold Cloned. It's in Vcenter but i can't power up that vm. I have plenty of resources so not sure where the issue lies. Any help is appreciated.

Thanks

Perry

[Texiwill]

Hello,

In the readme for the Update it states that HA will no longer evacuate VMs when going into maintenance mode. That is one issue. The other issue only occurs if your cluster goes from X number of hosts down to 1 host only. Then it will not autostart VMs. That is the bug. FOr the enterprise this is not common but for SMBs with only two nodes it is. This is known by VMware but not documented anywhere other than the forums and the specific SRs for the issue.

Upgrade to Update 1 if you only have 2-3 Nodes in your cluster.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[Chaton]

Hi,

have the same problem with the same error message (I've two ESX server in a cluster).

Do anyone know if HA has been fixed since september ?

Thanks for your help

Fred

[TiBoReR]

It is supposed to be fix in VirtualCenter 2.5 Update 3 which is available but I didn't test yet.

[Chaton]

Hi,

I think i've found the solution: in fact, the installation had been made by another IT. The problem was that he completed the /etc/sysconfig/network with uppercase entry because HA problems......

That's why the ./ft_getbyhostname failed.

After made the corrections and reboot the esx, i was able to active HA without errors and the ./ft_getbyhostname give me a correct entry (10.10.x.x. hostname)

Thank you for your answer, hope it'll help !