Refer to the Exhibit.
Users are having difficulty accessing a web server since a new web application was configured in a virtual machine running on sc-titanrum03.vmeduw.com.
The vSphere Client reports the error shown in the Exhibit. DRS is set to fully automated mode, but the problem has not resolved.
Which action can resolve the issue?
Hot-add a CPU to the the web server virtual machine.
Add an ESXi host to the cluster
vMotion one or more running virtual machines on the ESXi host running the web server virtual machine to the other ESxi host in the cluster.
Power off one or more virtual machine on the ESXi host running on the Web server virtual machine and migrate them to the other ESXi host in the cluster.
1. DRS isn’t moving
2. Host has CPU issue.
I first thought C would be the best option. However, if DRS isn’t moving anything then it doesn’t see that there would be enough of a performance gain. If you add another CPU it would help the VM. I wanted to note my observations:
1. 1 VM is experiencing the issue so there really isn’t CPU contention on the host
2. DRS doesn’t see any gains so how would moving help anything? So maybe adding that additional CPU would allow for a better DRS recommendation/move. meaning it would balance the cluster out.
3. An alarm doesn’t = bad just that it may be under load.