Why is the mem_overcommit kernel argument not interpreted properly when installing RHEV Hypervisor?

Solution Verified - Updated -

Issue

  • Attempting to use the mem_overcommit kernel argument when installing a RHEV hypervisor to specify the multiplier to use for adding extra swap to support memory over-commit
  • The SWAP logical volume is no different than when the hypervisor is installed with the default value (mem_overcommit=.5)

Environment

  • Red Hat Enterprise Virtualization Hypervisor 6.4 (20130318.1.el6_4)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.