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>
Cc: kvm@vger.kernel.org
Subject: Re: KVM and the OOM-Killer
Date: Fri, 14 May 2010 13:51:06 +0530	[thread overview]
Message-ID: <20100514082106.GG3296@balbir.in.ibm.com> (raw)
In-Reply-To: <4BED056B.1080804@jrcs.co.uk>

* James Stevens <James.Stevens@jrcs.co.uk> [2010-05-14 09:10:19]:

> >	echo "-16">  /proc/<pid>/oom_adj
> 
> Thanks for that - yes, I know about "oom_adj", but it doesn't
> (totally) work. "udevd" has a default of "-17" and it got killed
> anyway.
> 
> Also, the only thing this server runs is VMs so if they can't be
> killed oom-killer will just run through the everything else
> (syslogd, sshd, klogd, udevd, hald, agetty etc) - so on balance its
> a case of which is worse?  Without those daemons the system can
> become inaccessible and could become unstable, so on balance it may
> be better to let it kill the VMs.
> 
> My current work-around is :-
> 
> sync; echo 3 > /proc/sys/vm/drop_caches
>

Have you looked at memory cgroups and using that with limits with VMs? 

-- 
	Three Cheers,
	Balbir

  reply	other threads:[~2010-05-14  8:21 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 [this message]
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=20100514082106.GG3296@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).