2V0-620 · Question #77
Refer to the Exhibit. A 4 GB Memory virtual machine is experiencing extended memory issues, as shown in the Exhibit. What potential issues could be attributed to this memory pressure?
The correct answer is A. A limit is imposed on the virtual memory of this virtual machine. B. The Balloon driver has been uninstalled. A VM experiencing memory pressure can be caused by an imposed memory limit or a missing balloon driver, both of which force ESXi to use swap instead of efficient reclamation.
Question
Refer to the Exhibit. A 4 GB Memory virtual machine is experiencing extended memory issues, as shown in the Exhibit. What potential issues could be attributed to this memory pressure?
Exhibit
Options
- AA limit is imposed on the virtual memory of this virtual machine.
- BThe Balloon driver has been uninstalled.
- CA limit has been imposed on the Virtual CPU of the virtual machine.
- DStorage IO control has been enabled for the virtual machine causing the swapped memory.
How the community answered
(33 responses)- A67% (22)
- C12% (4)
- D21% (7)
Why each option
A VM experiencing memory pressure can be caused by an imposed memory limit or a missing balloon driver, both of which force ESXi to use swap instead of efficient reclamation.
When a memory limit is set below the VM's configured RAM, ESXi cannot allocate the full amount of physical memory to the VM, forcing it to balloon or swap memory to satisfy guest demands, which appears as memory pressure in performance charts.
The VMware balloon driver (vmmemctl) is the primary and least-disruptive memory reclamation technique; if it is uninstalled, ESXi must fall back to hypervisor swap, which causes severe performance degradation and the extended memory pressure symptoms shown in the exhibit.
A vCPU limit restricts processor scheduling for the VM but has no direct effect on memory allocation or swapping behavior.
Storage I/O Control manages disk I/O latency and bandwidth throttling and has no mechanism to cause or influence VM memory swapping.
Concept tested: VMware memory reclamation techniques and limits
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-A5C4C5D8-3F0C-4D5F-8E3C-5E1B8F9B8F1A.html
Topics
Community Discussion
No community discussion yet for this question.