A VM is experiencing delays even though its own CPU usage appears low.

CPU Ready measures the time during which a virtual CPU is prepared to execute but is waiting for the hypervisor to schedule it on a physical processor. A VM can therefore report low apparent CPU consumption while still responding slowly: its workload is not continuously executing because the assigned vCPUs are waiting for physical CPU time.

Elevated CPU Ready commonly indicates physical CPU contention, excessive vCPU allocation, an unfavorable vCPU-to-core ratio, or competition from other VMs on the host. The administrator should correlate CPU Ready with host CPU utilization, VM sizing, the number of runnable vCPUs, and workload behavior. Assigning additional vCPUs without confirming the cause can worsen scheduling delays because the hypervisor may need to coordinate more virtual processors.

Disk capacity measures available storage space and does not identify processor scheduling latency. Memory usage can reveal pressure, swapping, or insufficient guest memory, but it does not directly represent time spent waiting for CPU scheduling. Snapshot size relates to retained point-in-time storage data and is unrelated to hypervisor CPU dispatch. Nutanix identifies CPU Ready Time as the percentage of CPU wait time, making it the appropriate metric. Reference: Nutanix Intelligent Operations – VM Details and CPU Ready Time . NHCF alignment: workload performance interpretation.

===============