| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="ts_linux-host-malloc">
|
|---|
| 4 | <title>Linux Kernel vmalloc Pool Exhausted</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | When running a large number of VMs with a lot of RAM on a Linux
|
|---|
| 9 | system, say 20 VMs with 1 GB of RAM each, additional VMs might
|
|---|
| 10 | fail to start with a kernel error saying that the vmalloc pool
|
|---|
| 11 | is exhausted and should be extended. The error message also
|
|---|
| 12 | tells you to specify <codeph>vmalloc=256MB</codeph> in your
|
|---|
| 13 | kernel parameter list. If adding this parameter to your GRUB or
|
|---|
| 14 | LILO configuration makes the kernel fail to boot, with an error
|
|---|
| 15 | message such as <codeph>failed to mount the root
|
|---|
| 16 | partition</codeph>, then you have probably run into a memory
|
|---|
| 17 | conflict of your kernel and initial RAM disk. This can be solved
|
|---|
| 18 | by adding the following parameter to your GRUB configuration:
|
|---|
| 19 | </p>
|
|---|
| 20 | <pre xml:space="preserve">uppermem 524288</pre>
|
|---|
| 21 | </body>
|
|---|
| 22 |
|
|---|
| 23 | </topic>
|
|---|
