VM CPU Contention: Fix Slow VMs on Hyper-V & VMware

Too Many vCPUs Assigned to the VM

This is the number one cause of CPU contention. I see it all the time. Someone gives a VM 8 vCPUs because they think more is better. But that backfires. The hypervisor has to schedule all those vCPUs at the same time. If the host only has 4 physical cores, the VM fights for CPU time and loses.

You get high CPU ready times on VMware or high CPU wait times on Hyper-V. The VM feels sluggish even though the host isn't at 100%.

How to check it

1. On VMware, open vSphere. Find your VM. Look at the CPU Ready metric in the performance tab. Anything above 5% means trouble.
2. On Hyper-V, open Performance Monitor. Add the Hyper-V Hypervisor Virtual Processor\% Total Run Time counter for that VM. If it's below 80%, you have contention.

The fix

1. Shut down the VM.
2. Change the number of virtual CPUs to match what the VM actually uses. For a typical web server, 2 vCPUs is plenty. A database server might need 4. But never assign more vCPUs than the host has physical cores.
3. Start the VM. Watch the CPU ready time drop.

That change alone fixes 60% of CPU contention cases. Don't skip this step.

Noisy Neighbor VMs on the Same Host

Another VM on the same host is hogging CPU. Maybe it's running a backup job, a virus scan, or a bad loop. That one VM eats up cycles and leaves yours starving.

You'll see your VM's CPU ready time spike when the other VM is busy. It's not your VM's fault. It's a shared host problem.

How to find the culprit

1. On VMware, look at the host's CPU Ready chart. If it's high across multiple VMs, one is causing it. Sort VMs by CPU usage. The one at the top is the problem.
2. On Hyper-V, use Get-VMProcessor -VMName * in PowerShell. Check the PercentTotalRunTime for each VM.

The fix

1. If it's a backup or scan, reschedule it for off-hours.
2. If the VM always runs hot, move it to another host using live migration. On VMware, use vMotion. On Hyper-V, use Move-VM.
3. For permanent fix, set CPU limits on that noisy VM. On VMware, right-click the VM > Edit Settings > Resources > CPU. Set a limit to 50% of the host's capacity. On Hyper-V, set Set-VMProcessor -VMName NoisyVM -MaximumPercent 50.

This works fast. But be careful with limits. Too low and you'll slow down the noisy VM's workload. Start high and adjust.

Host CPU Saturation and Resource Limits

Sometimes the host itself is just hammered. Too many VMs packed on one server. CPU usage sits at 90% or higher all day. That leaves no room for spikes. Your VM gets CPU time only when others are idle.

You'll also see this if someone set a CPU limit or reservation on your VM. A limit is a cap. Even if the host has free CPU, your VM can't use more than the limit. A reservation guarantees CPU, but if it's set too low, your VM gets starved during competition.

How to check

1. Look at the host's overall CPU usage. On VMware, check the host summary. On Hyper-V, use Get-Counter "\Hyper-V Hypervisor Logical Processor(*)\% Total Run Time".
2. Check your VM's CPU limit and reservation. On VMware, go to VM settings > Resources. On Hyper-V, run Get-VMProcessor -VMName YourVM | fl *Limit*,*Reservation*.

The fix

1. If the host is overloaded, you need to add a new host to the cluster and move VMs over. Not instant, but necessary.
2. If your VM has a limit set, increase it. For example, change Limit from 50% to 100% if the host can handle it.
3. If you have a reservation, make sure it's reasonable. A small VM doesn't need a 4 GHz reservation. That wastes CPU for others.

One more thing: check if hyperthreading is on. If it is, each core counts as 2 logical processors. But a VM still needs a full core. So a host with 8 cores and hyperthreading has 16 logical processors. Don't oversubscribe beyond 8 VMs with 1 vCPU each. That's the rule of thumb.

Quick-Reference Summary