Source Knowledge From :- 
http://geekswing.com/geek/vmware-cpu-and-ram-reservations-fixing-insufficient-resources-to-satisfy-configured-failover-level-for-ha/

VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA

This post comes from a few days of poring over manuals as well as some technical support. This is a good one. The error came from trying to power on a VM in our VMware cluster and we would get these errors:
“Insufficient resources to satisfy configured failover level for HA”





And this alert on our cluster
“Insufficient resources to satisfy HA failover level on cluster vmCluster in vmTST”




Our way of thinking was we had to power one off to power another one on.
But that didn’t work.
Here we is the actual solution. (p.s. Great VMware HA education for me on this one!)

PROBLEM SOURCE: VMware HA is turned on and you are violating constraints

VMware HA is turned on, and you have it configured so that there is a certain amount of resource reserve for failover. By turning on this VM, you are going to dip into that resource reserve and so VMware is telling you “Nope, not turning it on….”
There is a quick fix to get the VM turned on (one good way, one bad way), and then there are two long term fixes for you to consider. In my case, the first one was faster, while the second one was better for my environment.

My VMware environment

Datacenter: vmTST
Cluster: vmCluster
OS: ESXi 4.1.0
Five (5) servers in a cluster.

My VMware Cluster Errors

As mentioned above:
“Insufficient resources to satisfy configured failover level for HA”
and
“Insufficient resources to satisfy HA failover level on cluster vmCluster in vmTST”

TWO WAYS TO DO QUICK FIX

1. Turning off HA (popular, and I would say WRONG)
2. Disable Admission Control (much better!!)

#1: Turning off HA (though I recommend against)

This is the solution I saw on some forums (including vmware forum). After looking at it more, I recommend against it and I’ll explain why, but here it is:

VSphere Client: Browse Inventory -> Hosts and Clusters

Edit VMware cluster settings

Right Click on Cluster name -> Edit Settings

Turning off HA

While this works, if you do this, whenever you turn it back on, it has to do a recalculation for the HA failover. Bad, especially for testing or doing temporary power ons.

#2: Disable “Admission Control” (better IMO)

Better to disable “Admission Control” so VMS will power on despite violating availability constraints. This way your HA is still on. In the long run, though, it is better to fix your issue.
Same window, but next bullet item on the left:

LONG TERM FIX: TWO WAYS

There are two things I ended up having to look at. One was pretty good long term fix and that I had found suggested on forums including VMware forums.
The second is the actual fix to my problem, the best one in the long term