According to the How to use the cvm_shutdown script web search result3, the cvm_shutdown script signals HA when shutting down the CVM (Controller VM) to forward the storage traffic to another healthy CVM. Instead of using sudo shutdown or sudo reboot commands, this script should be used to minimize I/O hits in user VMs running on the present hypervisor host. The cvm_shutdown -P now command will initiate the shutdown process on the CVM immediately. Therefore, if the administrator needs to perform an orderly shutdown of the CVM, they should execute this command from the CVM.

According to the web search results, one of the requirements for cross-hypervisor disaster recovery (CHDR) is to install and configure Nutanix Guest Tools (NGT) on all the VMs2. NGT configures the VM with all the required drivers for VM portability. Without NGT, the VMs may fail to boot after being migrated to a different hypervisor type.

According to the Troubleshoot high memory issues on Azure virtual machines web search result2, one of the common factors in a low memory situation is over-provisioning memory for a VM. Over-provisioning memory can cause memory pressure, which leads to swapping and degraded performance. Therefore, to fix this issue, the administrator should reduce the amount of memory assigned to the VM, based on the average hardware requirements for that operating system and application load.

Nutanix clusters are resilient to a drive, node, block, and rack failures because they use redundancy factor 2 by default, allowing Nutanix clusters to self-heal2. Failure scenarios can be thought of in terms of fault domains, which are the physical or logical parts of a computing environment or location that are adversely affected when a device or service experiences an issue or outage3. There are four fault domains in a Nutanix cluster: Disk, Node, Block, and Rack4. Block and Rack are two options that are available for expanding the failure domain level of a cluster. Block fault tolerance is enabled by default and ensures that data is replicated across different blocks in a cluster5. Rack fault tolerance has to be configured manually and ensures that data is replicated across different racks in a cluster4.

According to the Migration to a different processor web search result2, live migration of VMs depends on the source and destination hosts having the same CPU functions (CPU flags). Live migration requires the source and destination hosts to have CPUs from the same manufacturer, and only CPU functions which both hosts support are provided (same CPU generation, or by using VMware Enhanced vMotion Compatibility (EVC)). If the administrator adds a node with older generation processors to an existing AHV cluster with newer generation processors, then live migration of VMs is prevented between newer and older processors, unless EVC is enabled.