A constrained VM is one that does not have enough resources for the demand and can lead to performance bottlenecks. A VM is considered constrained when it exhibits one or more of the following baseline values, based on the past 21 days: CPU usage > 90% (moderate), 95% (severe) CPU ready time > 5%, 10% Memory usage > 90%, 95% Memory swap rate > 0 Kbps1. To provide adequate host resources, resize (increase) the constrained VMs1.

Nutanix provides two types of granular RBAC for AHV hosts: category based and cluster based3. Category based RBAC allows administrators to assign roles to users or groups based on categories, which are key-value pairs that can be applied to various entities in Prism Central, such as clusters, hosts, VMs, images, and networks. Categories can be used to group entities by different criteria, such as department, project, environment, or location. For example, an administrator can create a category key named Department and assign different values to it, such as Finance, Marketing, or Engineering. Then, the administrator can apply this category to different clusters or hosts and assign roles to users or groups based on this category. This way, users or groups can have different levels of access to different clusters or hosts depending on their department4.
Cluster based RBAC allows administrators to assign roles to users or groups based on specific clusters registered in Prism Central. For example, an administrator can create a role named Cluster Admin and assign it to a user or group for a particular cluster. This way, the user or group can have full access to that cluster and its hosts and VMs, but not to other clusters5.

AOS and M.2 Drives are two updates that can be done while avoiding a host reboot. AOS is the Acropolis Operating System that includes the hypervisor, storage and management components of the Nutanix cluster, and firmware and software updates can also be applied to it without requiring any host reboots