< Back | Next>
You need to troubleshoot an issue involving a critical VM performing poorly. You suspect the issue is related to memory contention due to high memory demand on the ESXi host. Currently, you do not have the option of migrating any VMs to other ESXi hosts. You also do not have the option of stopping any VMs.
- Use the vSphere Client to determine whether the VM is suffering from memory contention.
- Use the vSphere Client to determine whether the size of the ESXi host’s memory resources is insufficient to meet its current demand of its VMs.
- If the VM is suffering from memory contention that is caused by insufficient ESXi host memory, then correctly apply the following requirements:
- Do not stop any VM.
- Do not stop any service in a VM.
- Do not migrate any VM to another ESXi host.
- Do not add memory to the ESXi host.
- Fix the problem in a manner that ensures the critical VM will never need to use its VSWP file.
- Critical VM: vm-20
- ESXi host: host-01.lab.local
Objective: : 6.2 Troubleshoot CPU and Memory Performance
Click Here For Solution
- Use the performance graphs in the vSphere Client to examine the ballooning, decompression, and memory swap counters for the VM. The most critical counters are swap in rateand swap out rate. If these are greater than zero, the VM is suffering from memory contention.
- Use the performance graphs in the vSphere Client to examine the memory state of the ESXi host. If it is 3 (hard) or 4(low), then the ESXi host memory is insufficient to handle the current workload.
- Right-click the VM and select the Resources tab.
- Change the Memory > Reservation to a value that matches the amount of memory configured for the VM. (If the VM is configured with 2 GB memory, set the reservation to 2 GB.)