Note: Discussion successfully moved from VMware vCenter™ to vMotion & Resource Management
A limit trumps a reservation.
An expandable reservation is nothing more than an ability for a resource pool to request "free" reserved resources from its parent.
That means that expandable reservation can be active and a limit can be active at the same time. However the resource pool can request "free" reserved resources up to the limit.
Resource pool expandable reservation is enabled
Resource pool is configured with 40 GB of memory reservation
Resource pool is configured with 80 GB of memory limit.
The resource pool will provide 40GB of memory to its child objects (resource pools and VMs) from its own pool that is backed by physical memory.
Any resource pool or VM inside the resource pool that has a memory reservation configured (also applicable to vm memory overhead reservation) is request to the resource pool, if the 40GB pool is depleted, the resource pool will request resources backed by physical memory (reserved) from its parent.
It can do this until it reaches the 80GB.
The resource pool cannot utilize more than 80GB of physical memory protected by a reservation.
Hello Mr. Denneman,
I know this is a really old thread, I get an error when I try to send you a private message.
I have an idea related to resource groups, I started a thread here: Resource group idea, looking for feedback
You have some really good blog posts on this topic that go much deeper than anything else I can find online, most of which just re-iterates the function of resource pools and shares and some of the most common mistakes. So you seem like the person most likely to have an idea about this.
Thank you for your attention