From: Athanasius <kvm@miggy.org>
To: James Stevens <James.Stevens@jrcs.co.uk>
Cc: kvm@vger.kernel.org
Subject: Re: KVM and the OOM-Killer
Date: Fri, 14 May 2010 08:33:34 +0100 [thread overview]
Message-ID: <20100514073334.GE16563@miggy.org> (raw)
In-Reply-To: <4BEBEE8F.9050508@jrcs.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
On Thu, May 13, 2010 at 01:20:31PM +0100, James Stevens wrote:
> We have a KVM host with 48Gb of RAM and run about 20 KVM clients on it.
> After some time - different time depending on the kernel version - the
> VM host kernel will start OOM-Killing the VM clients, even when there is
> lots of free RAM (>10Gb) and free SWAP (>34Gb).
It seems going to a 64 bit kernel is what you want, but I thought it
worth mentioning the available method to say "try not to OOM-kill *this*
process":
echo "-16" > /proc/<pid>/oom_adj
I go through some convolutions in starting KVM VMs so that this gets
done automatically for them. It basically scores the process *way* down
for consideration to be OOM-killed. Handy if you might accidentally run
something on the KVM host that chews up all the available memory. It
should then get killed instead of the VMs. You can also use '-17' to
exclude the process from consideration entirely.
See <kernel source>/Documentation/filesystems/proc.txt for details.
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-05-14 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 12:20 KVM and the OOM-Killer James Stevens
2010-05-13 12:39 ` Avi Kivity
2010-05-13 13:39 ` James Stevens
2010-05-13 13:53 ` Avi Kivity
2010-05-13 18:55 ` David S. Ahern
2010-05-13 13:42 ` Johannes Stezenbach
2010-05-14 7:33 ` Athanasius [this message]
2010-05-14 8:10 ` James Stevens
2010-05-14 8:21 ` Balbir Singh
2010-05-14 8:43 ` James Stevens
2010-05-14 12:28 ` Balbir Singh
2010-05-14 13:01 ` James Stevens
2010-05-14 8:19 ` Balbir Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100514073334.GE16563@miggy.org \
--to=kvm@miggy.org \
--cc=James.Stevens@jrcs.co.uk \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.