VMware Cloud Community
superfoneguy
Contributor
Contributor
Jump to solution

ESXi 5.1 cannot start a VM with Admission Check Failed for Memory Resource error

I see that there have been a number of folks that have this error and adjusting the memory reservation for the VIM under System Resources has fixed this problem, but not for me. My reservation setting in the VIM process is '0'. Vitals:

Dell T110 II Server

4GB RAM

Intel Xeon CPU E31220 @ 3.10GHz

4 CPU Cores

500 GB hard drive

ESXi version 5.1

One Linux VM with 4GB RAM allocation, 2 CPU cores and 45 GB of storage.

Error I get upon attempted start:

Failed to power on VM.

Could not power on VM: Admission check failed for memory resource See the VMware ESX Resource management Guide for information management settings.

Group vm.4757: Invalid memory allocation parameters for VM vmm0:Mitel_Applications_Suite. (min: 524288, max: -1, minLimit: -1, shares:  -4, units: pages)

Group vm.4757: Cannot admint VM: Memory admission failed. requested reservation: 536579 pages

I have changed the VM memory all the way down to 1GB, no change.

I have played around with the VIM memory allocation, no change.

One interesting fact is that the Resource Allocation for the host tab shows memory @ 1747MB Capacity, Reserved Capacity @ 0MB and Available Capacity @ 1747MB, but I have 4GB of RAM and the vSphere Client does show that under the Configuration tab.

0 Kudos
1 Solution

Accepted Solutions
rcporto
Leadership
Leadership
Jump to solution

Take a look at this blog post: http://www.vmwarearena.com/2012/07/failed-to-power-on-vm-admission-check.html

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

0 Kudos
2 Replies
rcporto
Leadership
Leadership
Jump to solution

Take a look at this blog post: http://www.vmwarearena.com/2012/07/failed-to-power-on-vm-admission-check.html

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
superfoneguy
Contributor
Contributor
Jump to solution

Thanks you very much, that must be the only Google hit I didn't try. Allocating memory properly per the link you provided allowed me to start my VM. Thanks again.

0 Kudos