From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lukas Kolbe Subject: Re: kvm-84 and guests with more than 3536 MB Ram? Date: Tue, 24 Mar 2009 19:07:15 +0100 Message-ID: <1237918035.4577.14.camel@larosa> References: <1237897377.10977.40.camel@vesuv.TechFak.Uni-Bielefeld.DE> <49C8D94B.9090709@redhat.com> <1237906054.18072.8.camel@vesuv.TechFak.Uni-Bielefeld.DE> <49C90012.1020700@codemonkey.ws> <49C90490.1070906@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Avi Kivity , kvm@vger.kernel.org To: Tomasz Chmielewski Return-path: Received: from core.mokelbu.de ([85.10.222.94]:56832 "EHLO core.mokelbu.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757291AbZCXTa4 (ORCPT ); Tue, 24 Mar 2009 15:30:56 -0400 In-Reply-To: <49C90490.1070906@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Am Dienstag, den 24.03.2009, 17:04 +0100 schrieb Tomasz Chmielewski: > Anthony Liguori schrieb: > > Lukas Kolbe wrote: > >> On Di, 2009-03-24 at 14:59 +0200, Avi Kivity wrote: > >> > >>> Lukas Kolbe wrote: > >>> > >>>> Hi! > >>>> > >>>> This is my first post here so please bear with me; we have a Debian > >>>> Lenny system with kernel 2.6.28 and kvm-84, and can't start a guest > >>>> with > >>>> more than 3536 MB Ram. With kvm-72 (the version lenny released with) we > >>>> can use all 7GB that is intended for that guest. > > (...) > > >> qemu: loading initrd (0x781b93 bytes) at 0x000000007f87e000 > >> create_userspace_phys_mem: Invalid argument > >> kvm_cpu_register_physical_memory: failed > >> > >> And back to the console. When I try the same with 3584MB, I can boot > >> into the machine flawlessly. > >> > >> Sorry for getting the numbers wrong in the first mail - the actual > >> problem starts at 3585MB Ram for the guest. > >> > >> If you can't reproduce it with yout 2.6.28 and kvm-84, I should possibly > >> take this to the debian bugtracker ... > >> > > > > kvm-72 is pretty old. It used to be that we used phys_ram_base for > > loading kernel/initrds which would break when using > 3.5GB of memory. > > I wouldn't be surprised if that fix happened post kvm-72. > > Doesn't he say that it did work for him with kvm-72, but does not with > kvm-84? Exactly that :) kvm-72 works like a charm, with the noted exception that it crashes every now and than on our system (during heavy load), which was the reason we tried 084 in the first place. -- Lukas