The host is a P4 with 1gb. it ends up with 805mb available.
An adjustment to the "vim" settings turned out to be the problem. Links below to good hits on google and vmware sites.
This speaks of esxi 4.0, but uses the same terms with more info:
http://www.vm-help.com/esx40i/memory_allocation.php
Can't admit VM: Memory admission check failed
On a system with a lower amount of RAM you may find
that ESXi allocates too much to run the vmkernel and system services not
leaving sufficient memory for running VMs. In the below example, the
host has 3 GB of memory. ESXi is showing about 2600 MB available for
virtual machines. But an important number for virtual machines is the
memory capacity shown on the Resource Allocation in the 2nd image below.
This shows that my VMs have a total capacity of just over 1400 MB for
VM memory overhead. A chart of memory overhead per vCPU / VM memory is
shown below. VM memory overhead includes space for the VM frame buffer
and virtualization data structures like shadow page tables. Once my
running VMs have exhausted the 1400 MB of total capacity, I will not be
able to start additional VMs even though ESXi may have plenty of free
memory.
Virtual Machine Memory Overhead*
Memory(MB) | 1VCPU | 2VCPUs | 3VCPUs | 4VCPUs | 5VCPUs | 6VCPUs | 7VCPUs | 8VCPUs |
256 | 113.17 | 159.43 | 200.53 | 241.62 | 293.15 | 334.27 | 375.38 | 416.5 |
512 | 116.68 | 164.96 | 206.07 | 247.17 | 302.75 | 343.88 | 385.02 | 426.15 |
1024 | 123.73 | 176.05 | 217.18 | 258.3 | 322 | 363.17 | 404.34 | 445.52 |
2048 | 137.81 | 198.2 | 239.37 | 280.53 | 360.46 | 401.7 | 442.94 | 484.18 |
4096 | 165.98 | 242.51 | 283.75 | 324.99 | 437.37 | 478.75 | 520.14 | 561.52 |
8192 | 222.3 | 331.12 | 372.52 | 413.91 | 591.2 | 632.86 | 674.53 | 716.19 |
16384 | 334.96 | 508.34 | 550.05 | 591.76 | 900.44 | 942.98 | 985.52 | 1028.07 |
32768 | 560.27 | 863.41 | 906.06 | 948.71 | 1515.75 | 1559.42 | 1603.09 | 1646.76 |
65536 | 1011.21 | 1572.29 | 1616.19 | 1660.09 | 2746.38 | 2792.3 | 2838.22 | 2884.14 |
131072 | 1912.48 | 2990.05 | 3036.46 | 3082.88 | 5220.24 | 5273.18 | 5326.11 | 5379.05 |
262144 | 3714.99 | 5830.6 | 5884.53 | 5938.46 | 10142.83 | 10204.79 | 10266.74 | 10328.69 |
* taken from vSphere Resource Management Guide
Let's say I have a 1 vCPU VM with 2 GB of memory. ESXi
will need a memory overhead of about 137 MB to start the VM. But if I
give it 1400 MB memory reservation, then ESXi will need available
capacity of about 1537 MB to start the VM. In my case, the VM won't be
able to start and will display the error: Can't admit VM: Memory
admission check failed. I would need to have an available capacity of
more that 1537 MB to start the VM.
So if your host is experiencing this issue, but the
summary page for the host is showing that you have available memory you
can tweak the memory reservations for system processes to increase the
size of Memory: Total Capacity. Note that this is not a supported
procedure and underallocating system resources can have a negative
performance impact. Select the Configuration tab and then System
Resource Allocation. Click on the Advanced link in the top right hand
corner of the window to show advanced configuration options. In the
below image I have selected vmvisor object and am dropping the
reservation from 768 MB to 256 MB. After a few minutes the 512 MB of
memory freed up from the reservation will be available on the Resource
Allocation page. There are other objects which could be modified, but a
change to the vmvisor reservation can quickly yield 512 MB of free
memory. If an object does not let you reduce the reservation, you may
get an error or the number will remain unchanged after you click OK.
this hit is on point for the problem on 3.5
http://communities.vmware.com/thread/221202
Re: ESXi 3.5 : Admission Check Failed for Memory Resource
No comments:
Post a Comment