From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Subject: Re: KVM RAM limitation
Date: Wed, 3 Feb 2010 17:06:53 -0300 [thread overview]
Message-ID: <20100203200653.GG6798@defiant.freesoftware> (raw)
In-Reply-To: <4B69CC6C.2090506@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
Hi, Anthony.
On Wednesday, 03 February 2010 13:20:12 -0600,
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.
Regards,
Daniel
[1] https://help.ubuntu.com/community/KVM/Installation#Use%20a%2064%20bit%20kernel%20if%20possible
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-02-03 20:07 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 [this message]
2010-02-03 22:44 ` Brian Jackson
2010-02-04 17:47 ` Daniel Bareiro
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=20100203200653.GG6798@defiant.freesoftware \
--to=daniel-listas@gmx.net \
--cc=dbareiro@gmx.net \
--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.