public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Lukas Kolbe <l-lists@einfachkaffee.de>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: kvm-84 and guests with more than 3536 MB Ram?
Date: Tue, 24 Mar 2009 15:40:23 -0500	[thread overview]
Message-ID: <20090324204023.GE27104@us.ibm.com> (raw)
In-Reply-To: <1237918035.4577.14.camel@larosa>

* Lukas Kolbe <l-lists@einfachkaffee.de> [2009-03-24 14:32]:
> 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.

running kvm-84 with -m 8192 -- passes memtest on ubuntu 8.10 x86_64
server cd.  Maybe wrong bios?  From kvm-84 make install, I have:

% md5sum /usr/local/share/qemu/bios.bin 
470d43e4838be608a2447b23a9f83d90  /usr/local/share/qemu/bios.bin


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  reply	other threads:[~2009-03-24 20:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 12:22 kvm-84 and guests with more than 3536 MB Ram? Lukas Kolbe
2009-03-24 12:59 ` Avi Kivity
2009-03-24 14:47   ` Lukas Kolbe
2009-03-24 15:45     ` Anthony Liguori
2009-03-24 16:04       ` Tomasz Chmielewski
2009-03-24 18:07         ` Lukas Kolbe
2009-03-24 20:40           ` Ryan Harper [this message]
2009-03-24 21:02             ` Lukas Kolbe
2009-03-24 21:27               ` Ryan Harper
2009-03-25 19:25                 ` Lukas Kolbe

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=20090324204023.GE27104@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=l-lists@einfachkaffee.de \
    --cc=mangoo@wpkg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox