What is the advantage of leaving the mission critical virtual machines in the root resource pool?

A DRS cluster has been created with the following specifications:
• All mission critical virtual machines are in the root resource pool.
• All other virtual machines are placed into two child pools based on medium or low priority.
• The two child pools contain adequate resources needed by the medium and low priority virtual
machines.
• The two child pools are reserving 35% of the total available resources of the cluster.

What is the advantage of leaving the mission critical virtual machines in the root resource pool?

A DRS cluster has been created with the following specifications:
• All mission critical virtual machines are in the root resource pool.
• All other virtual machines are placed into two child pools based on medium or low priority.
• The two child pools contain adequate resources needed by the medium and low priority virtual
machines.
• The two child pools are reserving 35% of the total available resources of the cluster.

What is the advantage of leaving the mission critical virtual machines in the root resource pool?

A.
The root resource pool has immediate access to new physical resources added to the cluster.

B.
Virtual machines placed in the root resource pool have a higher vMotion priority in DRS.

C.
Transparent Memory Page Sharing in the root resource pool has a higher weight than in child
pools.

D.
Virtual machines placed in the root resource pool have higher default share values.

Explanation:



Leave a Reply 3

Your email address will not be published. Required fields are marked *


SMS

SMS

The correct answer is A.
The root resource pool has immediate access to new physical resources added to the cluster.

vmsatguru

vmsatguru

D is correct

What are the default share values of a root resource pool?
Answer is everything available (either be a host OR a DRS cluster)
All other 2 child resource pool will get any left over from this.

For the root resource pool, the values of the reservation and the limit are set by the system and are not configurable. The reservation and limit are set to the same value, indicating the total amount of resources the system has available to run virtual machines. This is computed as the aggregated CPU and memory resources provided by the set of current available hosts in the parent compute resource minus the overhead of the virtualization layer.
Ref: https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.ResourcePool.html