2V0-621 · Question #171
Refer to the Exhibit. An administrator is troubleshooting a CPU performance related problem for the SlowVM virtual machine. Which three actions should the administrator take to improve CPU performance
The correct answer is B. Decrease the number of vCPUs assigned to SlowVM. C. Power off other VMs running on the same ESXi host. E. Move SlowVM to another ESXi host with more physical CPU resources available.. When an SMP virtual machine exhibits high Co-Stop and Ready values due to over-allocated vCPUs, the correct remediation is to reduce the vCPU count, free host resources, or migrate to a less-loaded host.
Question
Refer to the Exhibit. An administrator is troubleshooting a CPU performance related problem for the SlowVM virtual machine. Which three actions should the administrator take to improve CPU performance for SlowVM? (Choose three.)
Exhibit
Options
- AIncrease the number of vCPUs assigned to SlowVM.
- BDecrease the number of vCPUs assigned to SlowVM.
- CPower off other VMs running on the same ESXi host.
- DIncrease the CPU limit for SlowVM.
- EMove SlowVM to another ESXi host with more physical CPU resources available.
How the community answered
(24 responses)- A21% (5)
- B67% (16)
- D13% (3)
Why each option
When an SMP virtual machine exhibits high Co-Stop and Ready values due to over-allocated vCPUs, the correct remediation is to reduce the vCPU count, free host resources, or migrate to a less-loaded host.
Increasing vCPUs on a VM that is already experiencing co-scheduling contention worsens the problem because the hypervisor must now find even more simultaneous free physical CPU threads.
Reducing the number of vCPUs on SlowVM decreases the co-scheduling burden, making it easier for the hypervisor to simultaneously schedule all vCPUs and lowering both Co-Stop and Ready values.
Powering off other virtual machines releases physical CPU threads on the host, directly reducing the scheduling pressure that causes Ready and Co-Stop contention for SlowVM.
Raising the CPU limit only helps if the VM is being throttled by an existing limit setting; the exhibit indicates the issue is scheduling contention, not a configured resource cap.
Migrating SlowVM to an ESXi host with more available physical CPU resources gives the scheduler more threads to work with, reducing wait times without requiring configuration changes to the VM.
Concept tested: Remediating SMP VM CPU co-scheduling contention in vSphere
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-671-resource-management-guide.pdf
Topics
Community Discussion
No community discussion yet for this question.
