Nutanix performance troubleshooting guidelines highlight CPU Ready Time as a key indicator of CPU contention. The documentation explains:
“High CPU Ready Time indicates that vCPUs are waiting to be scheduled on physical cores due to host CPU saturation or CPU overcommitment.”
CPU Ready Time doesnotrelate to storage issues or CVM sizing. Instead, it indicates that the hypervisor cannot schedule VM CPU operations promptly.
Internal extracts clearly describe the next diagnostic step:
“When CPU ready metrics rise, the first step is to check physical host CPU utilization to confirm whether the host is oversubscribed or running at high CPU usage.”
If the host is overloaded, remediation includes distributing VMs across hosts, reducing vCPU count on oversized VMs, or adding compute resources.
Other options are irrelevant:
Memory oversubscription is unrelated to CPU Ready Time.
SSD capacity affects storage latency, not CPU scheduling.
CVM CPU counts do not cause VM CPU Ready Time; CVM resource misconfiguration affects cluster services, not guest VM scheduling.
Thus, reviewing host CPU utilization is the correct next step.
