* KVM RAM limitation
@ 2010-02-03 15:55 Daniel Bareiro
2010-02-03 17:48 ` Brian Jackson
0 siblings, 1 reply; 8+ messages in thread
From: Daniel Bareiro @ 2010-02-03 15:55 UTC (permalink / raw)
To: KVM General
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hi all!
I'm trying to boot a VM with 2048 MB in a VMHost with Linux 2.6.32.6 and
qemu-kvm-0.12.2, but when doing it, I obtain it the following message:
qemu: at most 2047 MB RAM can be simulated.
This happened to me previously if in the VMHost I used kernel that is
not x86_64 [1], but it is not the case:
# uname -a
Linux wilson 2.6.32.6-dgb #1 SMP Mon Feb 1 17:10:30 ART 2010 x86_64 GNU/Linux
Which can be the problem?
Thanks in advance for your replies.
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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: KVM RAM limitation
2010-02-03 15:55 KVM RAM limitation Daniel Bareiro
@ 2010-02-03 17:48 ` Brian Jackson
2010-02-03 19:08 ` Daniel Bareiro
0 siblings, 1 reply; 8+ messages in thread
From: Brian Jackson @ 2010-02-03 17:48 UTC (permalink / raw)
To: dbareiro; +Cc: KVM General
On Wednesday 03 February 2010 09:55:41 am Daniel Bareiro wrote:
> Hi all!
>
> I'm trying to boot a VM with 2048 MB in a VMHost with Linux 2.6.32.6 and
> qemu-kvm-0.12.2, but when doing it, I obtain it the following message:
>
> qemu: at most 2047 MB RAM can be simulated.
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)
>
> This happened to me previously if in the VMHost I used kernel that is
> not x86_64 [1], but it is not the case:
>
> # uname -a
> Linux wilson 2.6.32.6-dgb #1 SMP Mon Feb 1 17:10:30 ART 2010 x86_64
> GNU/Linux
>
>
> Which can be the problem?
>
> Thanks in advance for your replies.
>
> Regards,
> Daniel
>
> [1]
> https://help.ubuntu.com/community/KVM/Installation#Use%20a%2064%20bit%20ke
> rnel%20if%20possible
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: KVM RAM limitation
2010-02-03 17:48 ` Brian Jackson
@ 2010-02-03 19:08 ` Daniel Bareiro
2010-02-03 19:20 ` Anthony Liguori
0 siblings, 1 reply; 8+ messages in thread
From: Daniel Bareiro @ 2010-02-03 19:08 UTC (permalink / raw)
To: KVM General
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On Wednesday, 03 February 2010 11:48:01 -0600,
Brian Jackson wrote:
> > I'm trying to boot a VM with 2048 MB in a VMHost with Linux 2.6.32.6
> > and qemu-kvm-0.12.2, but when doing it, I obtain it the following
> > message:
> >
> > qemu: at most 2047 MB RAM can be simulated.
> 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.
Thanks for your reply.
Regards,
Daniel
--
Daniel Bareiro - System Administrator
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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: KVM RAM limitation
2010-02-03 19:08 ` Daniel Bareiro
@ 2010-02-03 19:20 ` Anthony Liguori
2010-02-03 20:06 ` Daniel Bareiro
0 siblings, 1 reply; 8+ messages in thread
From: Anthony Liguori @ 2010-02-03 19:20 UTC (permalink / raw)
To: dbareiro, KVM General
On 02/03/2010 01:08 PM, Daniel Bareiro wrote:
> On Wednesday, 03 February 2010 11:48:01 -0600,
> Brian Jackson wrote:
>
>
>>> I'm trying to boot a VM with 2048 MB in a VMHost with Linux 2.6.32.6
>>> and qemu-kvm-0.12.2, but when doing it, I obtain it the following
>>> message:
>>>
>>> qemu: at most 2047 MB RAM can be simulated.
>>>
>
>> 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.
Regards,
Anthony Liguori
> Thanks for your reply.
>
> Regards,
> Daniel
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: KVM RAM limitation
2010-02-03 19:20 ` Anthony Liguori
@ 2010-02-03 20:06 ` Daniel Bareiro
2010-02-03 22:44 ` Brian Jackson
0 siblings, 1 reply; 8+ messages in thread
From: Daniel Bareiro @ 2010-02-03 20:06 UTC (permalink / raw)
To: KVM General
[-- 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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: KVM RAM limitation
2010-02-03 20:06 ` Daniel Bareiro
@ 2010-02-03 22:44 ` Brian Jackson
2010-02-04 17:47 ` Daniel Bareiro
0 siblings, 1 reply; 8+ messages in thread
From: Brian Jackson @ 2010-02-03 22:44 UTC (permalink / raw)
To: dbareiro; +Cc: KVM General
On Wednesday 03 February 2010 02:06:53 pm Daniel Bareiro wrote:
> 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.
>
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.
> Regards,
> Daniel
>
> [1]
> https://help.ubuntu.com/community/KVM/Installation#Use%20a%2064%20bit%20ke
> rnel%20if%20possible
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: KVM RAM limitation
2010-02-03 22:44 ` Brian Jackson
@ 2010-02-04 17:47 ` Daniel Bareiro
2010-02-04 18:27 ` Brian Jackson
0 siblings, 1 reply; 8+ messages in thread
From: Daniel Bareiro @ 2010-02-04 17:47 UTC (permalink / raw)
To: Brian Jackson; +Cc: KVM General
[-- 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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: KVM RAM limitation
2010-02-04 17:47 ` Daniel Bareiro
@ 2010-02-04 18:27 ` Brian Jackson
0 siblings, 0 replies; 8+ messages in thread
From: Brian Jackson @ 2010-02-04 18:27 UTC (permalink / raw)
To: dbareiro; +Cc: KVM General
On Thursday 04 February 2010 11:47:13 am Daniel Bareiro wrote:
> 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 covered two options for doing that in my last email. You either build a
static 64bit build on a 64bit host, or you install a 64bit chroot and
compile/run from there.
>
> 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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-02-04 18:27 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2010-02-04 18:27 ` Brian Jackson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox