Just a guess, but your Windows Os are 1 CPU and your Linux Guests are 2 or 4 vCPU right?

That's why making additional CPU in a VM isn't a good idea, they aren't being used. This isn't a VM thing, this is the ability of VM to see this information outside the OS. Most machines even though many have 2 or 4 CPU doesn't mean the software is making good use of those processors, which is why you shouldn't give CPU's just for the sake of adding CPU.

Well the ready time isn't bad per se, it's just an indication that the processors are ready to do something, but they have nothing to do. You will see high ready times in multi CPU environments.. One processor is typically always busy, even when it's idle. There are always tasks to perform. but 2 of them, makes things a bit more difficult because 1 processor even in a perfect Multi threaded world isn't going to be busy, simply because the machine has to be idle sometime.

So READY times are just an indication of this. Your processor(s) are just in ready state, but they aren't doing any work. It's like hiring city workers, only one of them does the work, the rest just soak up the air

To achieve best performance in a consolidated environment, you must consider ready time -

the time a virtual machine must wait in a ready-to-run state before it can be scheduled on a

CPU. This paper provides information to help you understand the factors that influence ready

time on an ESX Server 3.0 system

*
Processor Utilization versus Ready Time

*

The first test (Figure 1) shows how ready time changes with utilization. Six virtual machines were

running on the test server. All of them were pinned to a single CPU. Load was generated by the

CPU burner program run with a setting of approximately 15 percent, so that if it were the only

thing running, the virtual machine would consume close to 15 percent of the capacity of a

single CPU. Idle virtual machines also consumed some CPU capacity to perform guest operating

system maintenance tasks.

yes sire!

I updated my response, sir!