kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: James Stevens <James.Stevens@jrcs.co.uk>, kvm@vger.kernel.org
Subject: Re: KVM and the OOM-Killer
Date: Fri, 14 May 2010 13:49:54 +0530	[thread overview]
Message-ID: <20100514081954.GF3296@balbir.in.ibm.com> (raw)
In-Reply-To: <20100514073334.GE16563@miggy.org>

* Athanasius <kvm@miggy.org> [2010-05-14 08:33:34]:

> 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
> 

A lot of this is being changed, but not yet committed. There are
patches out there to deal with the lowmem issue. Meanwhile, do follow
the suggestions on oom_adj and moving to 64 bit.


-- 
	Three Cheers,
	Balbir

      parent reply	other threads:[~2010-05-14  8:20 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
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 [this message]

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=20100514081954.GF3296@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).