CloudInit is a package that contains utilities for early initialization of cloud instances. It allows you to customize virtual machines provided by a cloud vendor by modifying the generic OS configuration on boot. You can use CloudInit to set the OS hostname, add custom users, add keys, run custom scripts, and more2. CloudInit is supported by most major Linux and FreeBSD operating systems and works across different cloud platforms3. Sysprep is a tool for Windows operating systems that prepares an installation for cloning, auditing, and customer delivery4.
References: 1: Replacing Nodes in Nutanix Cluster - Nutanix Support & Insights 2: Customize a Linux VM with cloud-init in Azure - Azure Virtual Machines 3: Cloud-Init - The standard for customising cloud instances 4: Sysprep (Generalize) a Windows installation

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.

Based on the VM performance metrics shown in the exhibit, the most likely cause of the poor performance in the particular VM is that the host's CPU is severely overloaded. This is indicated by the high percentage of Hypervisor CPU Ready Time, which is shown as 96% in the CPU ready chart. CPU Ready Time is a metric that shows the amount of time a VM is ready to run but is unable to run because the host CPU resources are not available. In a healthy environment, this value is typically low. A high percentage indicates that the VMs are waiting for available CPU cycles, which means the CPU is not able to schedule the VM effectively, often due to overcommitment or heavy CPU load.
When the CPU ready time is consistently high, it is a clear indicator that the VM is frequently waiting for CPU resources, which can lead to performance issues such as sluggishness or delays in processing. It is not related to the storage subsystem (Oplog fullness or SSD tier size), nor directly to the number of vCPUs assigned to the VM. While adding more vCPUs might seem like a solution, it could actually exacerbate the issue if the host is already CPU constrained.
To resolve this issue, an administrator should consider balancing the load across the hosts more effectively, possibly by using Nutanix's built-in automation and balancing features, or by scaling out the cluster to add more CPU resources. It is also advisable to check for any VMs with unusually high CPU demand and to adjust resource allocation as needed. Nutanix provides extensive documentation and guidelines in their Resource Management Guide to help administrators identify and resolve such performance issues.

Configure VM-Host affinity for the nodes that meet the application's GPU requirement. This is because VM-Host affinity allows the administrator to specify which nodes a VM can run on or must not run on1. By creating a VM-Host affinity rule that binds the application VM to the three nodes that have the physical GPU, the administrator can ensure that the VM will always run on a node that meets its requirement, regardless of any HA or migration events. This also allows the other nodes in the cluster to host other VMs without any restrictions.