All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bareiro <dbareiro@uol.com.ar>
To: Brian Jackson <iggy@theiggy.com>
Cc: KVM General <kvm@vger.kernel.org>
Subject: Re: KVM RAM limitation
Date: Thu, 4 Feb 2010 14:47:13 -0300	[thread overview]
Message-ID: <20100204174713.GJ6798@defiant.freesoftware> (raw)
In-Reply-To: <201002031644.28348.iggy@theiggy.com>

[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]

Hi, Brian.

On Wednesday, 03 February 2010 16:44:28 -0600,
Brian Jackson wrote:

> > Anthony Liguori wrote:
> > >>> Are you sure you enabled KVM? Are you sure you are using the KVM
> > >>> binary and not some QEMU binary that's sitting around. This is one
> > >>> of those situations where the KVM command you are running might
> > >>> help.  Also the same binary you are running's version ($QEMU_BIN -h
> > >>> 
> > >>> | head -n1)

> > >> wilson:/usr/local/qemu-kvm/bin# ./qemu-system-x86_64 -h | head -n1
> > >> QEMU PC emulator version 0.12.2 (qemu-kvm-0.12.2), Copyright (c)
> > >> 2003-2008 Fabrice Bellard
> > >> 
> > >> 
> > >> The procedure that I used to compile qemu-kvm is the same of always:
> > >> to download qemu-kvm-0.12.2, to install the packages (Debian)
> > >> zlib1g-dev and libpci-dev, and to compile of the following way:
> > >> 
> > >> # cd qemu-kvm-0.12.2
> > >> # ./configure --prefix=/usr/local/qemu-kvm
> > >> # make
> > >> # make install
> > >> 
> > >> Until the moment I never got to use qemu-kvm with VMs of more than
> > >> 2048 MB. In an installation that I have with KVM-88 and kernel x86_64
> > >> I don't have this problem.

> > > QEMU and KVM only support 2GB of memory on a 32-bit host.
> > > 
> > > Both need to create a userspace mapping of the guests memory.  In a
> > > 32-bit environment, you only have enough usable address space in a
> > > process to create a 2GB region.
 
> > But, according to what I read in the link [1] that commented, just by to
> > have a x86_64 kernel would have to be sufficient to serve more than 2047
> > MB of RAM.

> The kvm userspace would also have to be compiled as a 64bit binary.
> Possibly statically compiled somewhere else (if that's even possible)
> or with a 64bit chroot.

Hmmm... and there is some way to compile qemu-kvm as a 64bit binary on a
operating system userspace of 32bit?

I tried with ARCH=x86_64 with make but when using this I obtain several
messages of the type "cast to/from pointer from/to integer of different
size".

Thanks for your reply.

Regards,
Daniel
-- 
Mi frase del día:
An algorithm must be seen to be believed.
		-- D. E. Knuth

Daniel Bareiro - GNU/Linux registered user #188.598
Proudly running Debian GNU/Linux with uptime:
14:02:40 up 31 days, 22:47, 11 users,  load average: 0.00, 0.02, 0.00

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-02-04 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 15:55 KVM RAM limitation Daniel Bareiro
2010-02-03 17:48 ` Brian Jackson
2010-02-03 19:08   ` Daniel Bareiro
2010-02-03 19:20     ` Anthony Liguori
2010-02-03 20:06       ` Daniel Bareiro
2010-02-03 22:44         ` Brian Jackson
2010-02-04 17:47           ` Daniel Bareiro [this message]
2010-02-04 18:27             ` Brian Jackson

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=20100204174713.GJ6798@defiant.freesoftware \
    --to=dbareiro@uol.com.ar \
    --cc=dbareiro@gmx.net \
    --cc=iggy@theiggy.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 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.