(re-adding list) On 04/15/2011 07:28 AM, Neal Murphy wrote:
On Wednesday 06 April 2011 03:35:27 you wrote: > On 04/06/2011 06:22 AM, Neal Murphy wrote: > > ENVIRONS: > > I'm running > > > > - Debian Squeeze. > > - QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5) > > - 2.6.32-5-686-bigmem #1 SMP Tue Mar 8 22:14:55 UTC 2011 i686 > > GNU/Linux - Quad Phenom II 965, 8GB RAM > > > > I'm booting generic 2.6.35.11 through syslinux. The command is generated > > via a script I wrote. It works fine until I assign more than 1005M RAM > > to the VM; it's been working fine (at less than 1GB RAM) for many > > months. The system I am booting boots and runs fine on bare metal. > > > > I got the same results when I DLed and installed ver. 0.14. > Looks like a guest BIOS issue. > > Please try qemu-0.14. Also try -cpu qemu64 instead of phenom. > > If those fail, we can attach with gdb and try to look at what's going > on, but let's try the simple tests first. BTW, is there a preferred 'set' of options to feed ./configure?
No.
I used './configure --prefix=/opt/kvm --enable-kvm' to build. Finally got my system (Smoothwall/Roadster) stabilized and out the door, so I have time to dedicate to this. OK. I've built 0.14 (installed to /opt/kvm and I deleted Squeeze's older package) and am using Squeeze's kvm_amd module. I tried without -cpu and -smp; I tried -cpu qemu64. I eliminated the -vga and -serial options to no avail. It still chokes on 1005MB RAM.
Works for me. Please use -monitor stdio and issue the commands (qemu) info registers (qemu) x/50i $eip - 30
So what's the next ste... ... Wait, just thought of something to try: 'rmmod kvm-amd'. ... Oho! Without the accelerator, it runs with at least 1588M RAM, but can't allocate 2000M RAM (this may be expected on a 32-bit OS with PAE).
2G limit is expected on i386.
Does this help? Is it time to submit a debian bug?
If debian fixes the bug, that would be great. -- error compiling committee.c: too many arguments to function -- 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
