Max number of powered-on VMs in 4.0

[sundarg]

What's the limit for the number of Powered-On VMs on ESXi 4.0 (Vsphere 4.0) ?

As per this document : http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf

it is supposed to be 320, but I'm not able to power on more than 170.

I get "no sufficient memory resources", "memory admission check failed" and such errors though only around 10-11 GB of 16 GB is consumed on the host.

These VMs have a very small footprint (Damn Small Linux with minimum possible configuration).

In ESXi 3.5 looks like the limit was 170 but is it a coincidence that 4.0 behaves like 3.5 ?

Thanks,

Sundar

[Dave_Mishchenko]

Welcome to the VMware Communities forums. What sort of memory numbers do you see on the Resource Allocation tab for the host in the vSphere client?




Dave

VMware Communities User Moderator

Now available - vSphere Quick Start Guide

Do you have a system or PCI card working with VMDirectPath? Submit your specs to the Unofficial VMDirectPath HCL.

[pcerda]

Hi,

Check the Resource Allocation on your VMs, especifically the reservation of memory. If you allocate all of physical memory of your ESXi, you could get this behavior.

This is different to the memory comsumption of your ESXi.

Regards / Saludos

-

---

Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!

VMware VCP-410

Join to Virtualizacion en Español group in Likedin

See My Blog

See My Linkedin Profile

-

---

Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[sundarg]

I have attached the screenshots for both host & VM.

(not sure why the VM says Reservation 82 MB under Reservation Settings : under Resource Tab for memory from edit-settings menu, there's no reservation at all)

Thanks,

Sundar

[pcerda]

Hi,

Please check the Resource Allocation tab on the Cluster and check the memory reservation.

In the other hand, if you have your cluster with HA enabled, check the Admission Control and Admission Control Policy settings, this can cause the behavior that you are seeing.

Check the Availability Guide of VMware documentation, especifically on page 13.

I attach some screenshots.

Regards / Saludos

-

---

Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!

VMware VCP-410

Join to Virtualizacion en Español group in Likedin

See My Blog

See My Linkedin Profile

-

---

Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[sundarg]

I did & have attached the screenshots.

HA or DRS are not (yet) enabled.

Thanks,

Sundar