Human resources users report their payroll system is running slow. An administrator monitors performance and notices the VM that runs the payroll system is showing very high memory utilization…

Memory hard limits cap the maximum RAM a VM can consume, which restricts individual VM growth but does not add physical memory to the host or resolve the underlying overcommitment that is causing swap activity.

When adding memory to a VM causes the host to engage in heavy swap file activity, the host's physical RAM is overcommitted - meaning the total VM memory allocations exceed available host RAM. Increasing physical memory on the virtualization host is the correct solution because it eliminates the root cause of overcommitment, restoring stable performance across all VMs without degrading any business unit.

Memory soft limits allow VMs to borrow extra memory when available and reclaim it under pressure, but they do not provide additional physical RAM to resolve host-level overcommitment.

Reducing memory on all other VMs degrades their performance across business units and is only a workaround, not a solution to the fundamental insufficiency of physical RAM on the virtualization host.