LeoJBI wrote:
There is no way for a VM to dynamically expand its memory
Therefore, what is the purpose of Resource Allocation? You are telling me that the memory needs to be defined from the initial
configuration?
My confusion is; If I have 8gb assigned to a VM and than set my Resource Allocation to 8gb, I have a total of 16gb available to a particular VM?
The additional 8gb can be available to other VM's when not in use?
My challenge is that I can potentially have three users needing the resources. However, most of the time there will be fewer than three VM's running. But from the user's perspective, they would rather use a physical machine because it is going to run faster that the one configured via a VM. 8gb of memory is just the minimal requirement. One of those challenges from me is memory allocation.
Thank you for your input.
Your boundary is always what is configured for a VM. If you set 8GB for a VM in a 24GB resource pool, then that VM can get at most 8GB is that is what you configured it for.
Resource Pools are designed to provide resource seperation between groups of VMs. So you wouldn't create just 1 resource pools but multiple. By using reservations / limits / shares you can carve up resources as desired.