CPU Co-Stop VMware is a VMware vSphere metric indicating time a multiprocessor VM waits for its vCPUs to be coordinated before execution.
Simple definition
CPU Co-Stop VMware is a VMware vSphere metric indicating time a multiprocessor VM waits for its vCPUs to be coordinated before execution. It belongs to the Virtualisation / Conteneurs vocabulary and is useful when reading architecture diagrams, product documentation, logs, or administration procedures.
What is it used for?
Its main purpose is to detect a VM oversized in vCPUs or scheduling constraints that degrade performance. The practical value depends on the surrounding architecture, security model, and operational requirements.
How does it work?
The ESXi scheduler must provide CPU time to vCPUs under co-scheduling rules. High co-stop can indicate that too many vCPUs make coordination harder.
Key points
- Scope: A VMware vSphere metric indicating time a multiprocessor VM waits for its vCPUs to be coordinated before execution.
- Operational goal: Detect a VM oversized in vCPUs or scheduling constraints that degrade performance.
- Implementation: The ESXi scheduler must provide CPU time to vCPUs under co-scheduling rules. High co-stop can indicate that too many vCPUs make coordination harder.
Points to watch
Analyze co-stop together with CPU Ready, actual usage, and host contention before changing vCPU count.
In short
CPU Co-Stop VMware = a VMware vSphere metric indicating time a multiprocessor VM waits for its vCPUs to be coordinated before execution. Use it when you need to detect a VM oversized in vCPUs or scheduling constraints that degrade performance.