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.
Is this a known bug? Someone on freenode #kvm said he'd seen something
like this but couldn't remember where or when.
Can you describe the failure? I just booted a guest (FC6) with 6GB,
without issue (admittedly the guest is only using 300MB or so).
Well, when I start the guest like this:
kvm -smp 8 -drive if=virtio,file=/dev/system/test_root,boot=on -m 3585 \
-nographic -name test -kernel /boot/kvm/test/vmlinuz-2.6.28-1-amd64 \
-initrd /boot/kvm/test/initrd.img-2.6.28-1-amd64 \
-append 'root=/dev/vda ro console=ttyS0,115200' \
-serial mon:unix:/etc/kvm/consoles/test.sock,server,nowait \
I get the following output:
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.
Regards,
Anthony Liguori
--
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
