Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 179681

Need Help..problem booting up VM in HA cluster..

$
0
0

Hi Experts.

 

We landed up in a strange bizarre scenario.

 

Few of our VM complain to power-up in an HA cluster

Quick lookup for vmware KB pointed me to http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033634

 

This exactly matched my problem.

Insufficient resources to satisfy configured failover level for vSphere HA

The operation would violate the configured failover level of the vSphere HA cluster. Either change the admission control policy to reserve fewer resources for failover or add more hosts to the cluster. 

Check the CPU and Memory reservations of the virtual machine in question.  As a virtual machine starts up, slot calculation will be affected and fewer slots will be available when a machine with high reservation values is started.

 

As mentioned i tried changing the admission control policy

 

first thing i did was turning off (disable Admission control option)

But i realized turning this off isn't solving the problem but its going to create more as my vm's would be secured

 

the KB doesnt help me ... what should i keep the admission changed too

 

i looked for best prac guide

 

http://www.vmware.com/files/pdf/techpaper/vmw-vsphere-high-availability.pdf

 

page 16 of this

 

percentage_of.png

 

i gave random % of 10 - 10 each for both CPU and RAM .. and power up my VM's in HA cluster.

 

now my questions

1. Did i do the right thing by keeping 10 % each ?

2. What should be the ideal number considering 10 ESX servers and close to 20 vm 's running on each

3. How do i arrive at right percentage

4. Can you please explain each of the admission control policy with an example. (i understand the third one.. its very simple... )

 

-Sr


Viewing all articles
Browse latest Browse all 179681

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>