* Lukas Kolbe <l-lists@xxxxxxxxxxxxxxxx> [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@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
