but look of it with only 1 physical CPU and you have 33 VM, it would be over assignment of vCPUs.
1 person found this helpful
First let me say that sounds like an awful lot of VMs to me for that size system, if they are mostly Windows Server 2003 and are all running at once. Also, be aware that if you run a VM with 2 vCPUs assigned to it, two physical cores must be available for it to run. If you have a lot of 2 vCPU VMs, on a system without a lot of physical cores, it can result in a situation where you don't see a high CPU utilization, yet things appear to be waiting on CPU, because only a few of the VMs can ever be running at once. Also, are you sure you aren't having a paging/swapping problem? That many server 2003 VMs running at once are going to need a lot of memory.
CPU wait time is the amount of time a virtual machine did get scheduled but the processors have
nothing to process and so the CPU simply waits while the scheduled time for the virtual
machine clicks by.
CPU Ready is the time that the virtual machine was ready, but could not get scheduled to run on the physical CPU.
bascially cpu ready means the guest is waiting on the host, cpu wait means the host is waiting on the guest.