The goal of the VMM cluster overcommit check is to determine whether there is any possibility that virtual machines will not be restarted if there is a concurrent failure of cluster reserve ( R ) nodes. The cluster is assumed to be overcommitted until proven otherwise. Four approaches are tried, and if any approach can show that the cluster is not overcommitted then the cluster state is set to "OK", otherwise the cluster state is set to "Overcommitted."
For details on each of the four calculations please see the following:
KB3023928 - Details of the cluster overcommit algorithm in System Center 2012 R2 Virtual Machine Manager ( http://support.microsoft.com/kb/3023928 )
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter :
Main System Center blog: http://blogs.technet.com/b/systemcenter/
Configuration Manager Support Team blog:
http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog:
http://blogs.technet.com/dpm/
Orchestrator Team blog:
http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog:
http://blogs.technet.com/momteam/
Service Manager Team blog:
http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog:
http://blogs.technet.com/scvmm
Microsoft Intune:
http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog:
http://blogs.technet.com/sus/
RMS blog:
http://blogs.technet.com/b/rms/
App-V Team blog:
http://blogs.technet.com/appv/
MED-V Team blog:
http://blogs.technet.com/medv/
Server App-V Team blog:
http://blogs.technet.com/b/serverappv
Forefront Endpoint Protection blog:
http://blogs.technet.com/b/clientsecurity/
Forefront Identity Manager blog:
http://blogs.msdn.com/b/ms-identity-support/
Forefront TMG blog:
http://blogs.technet.com/b/isablog/
Forefront UAG blog:
http://blogs.technet.com/b/edgeaccessblog/
Application Proxy blog:
http://blogs.technet.com/b/applicationproxyblog/
The Surface Team blog:
http://blogs.technet.com/b/surface/