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 17:58:01 +0530 [thread overview]
Message-ID: <20100514122801.GH3296@balbir.in.ibm.com> (raw)
In-Reply-To: <4BED0D18.80209@jrcs.co.uk>
* James Stevens <James.Stevens@jrcs.co.uk> [2010-05-14 09:43:04]:
> >Have you looked at memory cgroups and using that with limits with VMs?
>
> The problem was *NOT* that my VMs exhausted all memory. I know that
> is what "normally" triggers oom-killer, but you have to understand
> this mine was a very different scenario, hence I wanted to bring it
> to people's attention. I had about 10Gb of *FREE* HIGH and 34GB of
> *FREE* SWAP when oom-killer was activated - yep, didn't make sense
> to me either. If you want to study the logs :-
>
I understand, You could potentially encapsulate all else - except your
VM's in a small cgroup and frequently reclaim from there using the
memory cgroup. If drop caches works for you, that is good too. I am
surprised that cache allocations are causing lowmem exhaustion.
--
Three Cheers,
Balbir
next prev parent reply other threads:[~2010-05-14 12:28 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 [this message]
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=20100514122801.GH3296@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).