All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: James Stevens <James.Stevens@jrcs.co.uk>
Cc: kvm@vger.kernel.org
Subject: Re: KVM and the OOM-Killer
Date: Thu, 13 May 2010 16:53:17 +0300	[thread overview]
Message-ID: <4BEC044D.4070004@redhat.com> (raw)
In-Reply-To: <4BEC0121.2020700@jrcs.co.uk>

On 05/13/2010 04:39 PM, James Stevens wrote:
>> I'd go with 64-bit at 2GB and above. It's both faster and safer.
>
> safer, how? (apart from no lowmem exhaust).

Nothing apart from that (well, if you run nonpae you lose NX protection).

>
> 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 documentation is outdated.

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

You can run 32-bit userspace with a 64-bit kernel, or reinstall, 
whichever you prefer.

I once upgraded a 32-bit Fedora install to 64-bit, but that takes some 
tinkering.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-05-13 13:53 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 [this message]
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=4BEC044D.4070004@redhat.com \
    --to=avi@redhat.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 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.