Several virtual machines are slow at the same time. The host CPU stays busy, and the host still has free memory and free disk. Which limit fits?
Select an answer to reveal the explanation.
Short Explanation
The guests are all waiting on the same busy processor, and memory and disk are not the line. You are short on host CPU. A port-test plug, a disk stripe, and a screen setting do not explain a pegged processor.
Full Explanation
When many guests are slow and the host CPU stays busy while memory and disk are free, the host does not have enough processor for the guests that are running. A loopback plug tests a network port. It does not consume the host CPU on behalf of every guest. RAID 0 stripes disks. It is not a CPU limit, and the disk is free in this stem. Refresh rate is a display timing. Changing it does not free processor time for guests. Exam caveat: giving every guest many virtual CPUs can make this worse. Fit the guest CPU count to the host instead of copying a huge count onto every machine. Operational check: watch the host CPU during the slowdown, reduce the running guests or their virtual CPU counts, and confirm the remaining guests speed up. Reduce the number of running guests and confirm the ones that remain speed up.