From: James Stevens <James.Stevens@jrcs.co.uk>
To: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: KVM and the OOM-Killer
Date: Thu, 13 May 2010 14:39:45 +0100 [thread overview]
Message-ID: <4BEC0121.2020700@jrcs.co.uk> (raw)
In-Reply-To: <4BEBF2F8.7020507@redhat.com>
> I'd go with 64-bit at 2GB and above. It's both faster and safer.
safer, how? (apart from no lowmem exhaust).
On a different subject, the qemu documentation says a guest VM can only
have 2Gb of memory - does this still apply when using a 64bit host O/S ?
> The lowmem load is about 0.5% of guest memory, so 48GB means 240MB
> lowmem allocated. Thin ice.
We currently only have about 12Gb used by the VM guests, so not hitting
that issue - the rest of HIGHMEM is host disk cache.
Our experience is that the bottle-neck on number of VM guests is disk
i/o - with loads of memory we've pretty much eliminated reads, so that
means disk writes.
> Since you can run a 64-bit kernel with your existing userspace, at least
> you have a simple upgrade path.
Not sure I like the idea of running a 64bit user space kernel on top of
a 32bit host, prefer to re-install.
Can I just replace my kernel with a 64bit one, or do I have to
re-install the host O/S ?
James
next prev parent reply other threads:[~2010-05-13 13:39 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 [this message]
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
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=4BEC0121.2020700@jrcs.co.uk \
--to=james.stevens@jrcs.co.uk \
--cc=avi@redhat.com \
--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).