VMware

VMware GSX Server 2.5.2


Features | Documentation | Knowledge Base | Discussion Forums

previous Prev   Contents   Last   Next next

 Using More than 1GB of Memory on a Linux 2.2.x Kernel Host

Using More than 1GB of Memory on a Linux 2.2.x Kernel Host

By default, Linux kernels in the 2.2.x series support 1GB of physical memory. If you want to use more memory on a Linux host with a kernel in the 2.2.x series, you can take one of several approaches.

  • Upgrade to a 2.4.x series kernel that allows for more physical memory.

  • Recompile your kernel as a 2GB kernel using the CONFIG_2GB option.

  • Enable the CONFIG_BIGMEM option to map more physical memory. (This approach requires you to complete specific steps, described in detail in the Workarounds section below; otherwise, GSX Server cannot work on such a kernel.)

The CONFIG_2GB option calls for recompiling your kernel as a 2GB kernel. You do this by recompiling your kernel with CONFIG_2GB enabled. This allows Linux to support nearly 2GB of physical memory by dividing the address space into a 2GB user chunk and 2GB kernel chunk (as opposed to the normal 3GB user and 1GB kernel).

The third approach uses the CONFIG_BIGMEM option in Linux. With the CONFIG_BIGMEM option enabled, the kernel does not directly address all of physical memory and it can then map 1GB (or 2GB) of physical memory into the address space at a time. This allows the use of all of physical memory at the cost of changing the semantics the kernel uses to map virtual to physical addresses. However, VMware products expect physical memory to be mapped directly in the kernel's address space and thus do not work properly with the CONFIG_BIGMEM option enabled.

Workarounds

Workarounds

If you are using a 1GB kernel with CONFIG_BIGMEM enabled and have 960MB to 1983MB of memory, GSX Server does not run. To work around this issue, you can try one of the following:

  • Recompile the kernel as a 2GB kernel by enabling the CONFIG_2GB option. This allows for 100 percent use of physical memory.

  • Pass the boot-time switch mem=959M at the LILO prompt, or add it to lilo.conf, to disable CONFIG_BIGMEM and thus allow you to run GSX Server. To do this:

    • At the LILO prompt, type linux-2.2.16xxx mem=959M.
    • Or, edit lilo.conf. In the kernel section, add this line:
      append mem="959M"

If you have a 1GB kernel with CONFIG_BIGMEM enabled and have more than 1983MB of memory, you can do one of the following:

  • Recompile the kernel as a 2GB kernel by enabling the CONFIG_2GB option and either pass the boot-time switch mem=1983M at the LILO prompt or add it to lilo.conf. To use the switch:

    • At the LILO prompt, type linux-2.2.16xxx mem=1983M.
    • Or, edit lilo.conf. In the kernel section, add this line:
      append mem="1983M"

  • Pass the boot-time switch mem=959M at the LILO prompt or add it to lilo.conf to disable CONFIG_BIGMEM. To use the switch:

    • At the LILO prompt, type linux-2.2.16xxx mem=959M.
    • Or, edit lilo.conf. In the kernel section, add this line:
      append mem="959M"

If you are using a 2GB kernel with CONFIG_BIGMEM enabled and have 1984MB or more memory, GSX Server does not run. You can either pass the boot-time switch mem=1983M at the LILO prompt, or add it to lilo.conf, to disable CONFIG_BIGMEM and thus allow you to run GSX Server. To use the switch:

  • At the LILO prompt, type linux-2.2.16xxx mem=1983M.

  • Or, edit lilo.conf. In the kernel section, add this line:
    append mem="1983M"

previous Prev   Contents   Last   Next next