VMware

This Question is Answered

1 2 Previous Next 23 Replies Last post: Oct 6, 2008 8:58 AM by a.c.  

Update 2 VMWare HA Oddness... Not enough resources posted: Aug 23, 2008 7:16 AM

Click to view Texiwill's profile Guru 10,236 posts since
Jan 13, 2004
Hello,

I have an issue that is quite bizarre. My cluster consists of 2 DL380G5s with 16GBs each and 2 quad core pCPUs. I have VMware HA enabled and I was trying to determine why failover did not occur when I lost one node. VMware HA is configured to allow up to 1 host failure and VMs can start if availability constraints are violated. Everything is the default settings otherwise.....

I can start several VMs after a reboot of the single node but after a bit of time I get 'Not Enough Resources'. Now this message occurs until I bring the 2nd node back into the cluster. This seems very odd to me. It is for this reason I have VMware HA capability so why is it telling me I have not enough resources? When I clearly have plenty of resources. Currently using about 1Ghz out of 8x2.333Ghz and 5.33GB out of 16GB of memory.

I thought perhaps it was an issue with the HA cluster so I rebuilt it per the KB Article (i.e. deleted the old cluster and created a new one, adding back in the host). I was able to boot VMs for a short while, then once more got into this state. I have also gone through and verified all the resources on all powered on and powered off VMs are set to the default and 'Normal' settings. One other item I have 6 Resource Pools all 'Normal & Expandable' plus 2 Resource Pools under one of them. All others have no child resource pools. It makes no difference in which resource pool I attempt to boot a VM even the parent pool of the cluster gives the same error 'Insufficient Resources'

I just fixed the other node, brought it in and all is now fine, but this is not proper. I should be able to still boot VMs anytime.... I used to be able to do so until I upgraded to Update 2. This is indeed a puzzler for me, everything looks just fine and works for a short period after boot, which is in itself peculiar.

I can reproduce this by placing the 2nd node in Maintenance mode as well.


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
Click to view ThompsG's profile Hot Shot 194 posts since
Feb 2, 2005

Hi,

I believe they (VMware) have tighten the thumbs screws around HA in Update 2. If you read the Known Issues in VMware Infrastructure 3 Release Notes (http://www.vmware.com/support/vi3/doc/vi3_esx35u2_vc25u2_rel_notes.html#knownhaissues) you can see that other issues have arisen around this.

Kind regards,

Glen

Click to view weinstein5's profile Guru 6,351 posts since
Nov 19, 2005
Unless I did not see it - do you have any reservations set either on the Resource Pools or VMs?
Click to view ThompsG's profile Hot Shot 194 posts since
Feb 2, 2005

Hi,

As mentioned, the link was not directly related to your problem, however was hi-lighting that there is an issue around HA, Update 2 and failover. Too me, it appears that VMware have changed the parameters around HA and even if you (believe you) have enough resources to run all VM's of one host. Update 2 seems to have lowered the threshold for resources, which is highly annoying.

We have experienced the same problem you have, but thankfully most of our clusters have more than 2 hosts so it doesn't effect us as much as other customers.

Best regards,

Glen

Click to view ThompsG's profile Hot Shot 194 posts since
Feb 2, 2005

Hi,

Not sure if you are still chasing this one or not but found this while browsing the forums tonight. Seems to give a better explanation as too what is happening here: http://communities.vmware.com/thread/160824?tstart=0

Part way down this post, it gives how VMware are now calculating failover.

Trust this helps and not makes it worse.

Kind regards,

Glen

Click to view eziskind's profile Expert 310 posts since
Feb 21, 2006
This is a known issue in U2 which will be fixed in a future patch/update release. The root cause of the issue in this thread and the one described in the other thread you mentioned is the same. The basic issue is that in an HA-DRS cluster, even when HA admission control is turned off (ie. you're allowing vms to power on even if it violates the HA constraint) DRS will still reserve some failover capacity for HA. This prevents vms from being automatically evacuated off a host entering maintenance mode (though you should be able to migrate them manually) and powering on vms in some cases.
Click to view zemotard's profile Expert 570 posts since
Jan 9, 2006
I have had same error when my Host had an hardware problem.
I hope this issue will be soon release ...

This update 2 is really not prefect ...
Click to view Randy_B's profile Hot Shot 159 posts since
Feb 1, 2005
Has there been any word from Vmware on when a patch for this issue will be released?
Click to view a.c.'s profile Enthusiast 21 posts since
Mar 3, 2008

Hello,

VMware is aggressively working to release a fix ASAP, however we are unable to provide a timeline at the moment. Please do contact the VMware support team if you have further questions. Rest assured, this fix will be available soon!

Thanks,

The VMware Team

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities