On Fri, Jan 22, 2010 at 11:13 AM, Corey Minyard <minyard@xxxxxxx> wrote: > > I tried using telnet for the console, and it worked for a little while: > > root@ebony:~# ./qemu-system-ppcemb --enable-kvm -nographic -m 128 -M bamb > oo -kernel uImage.bamboo -L . -append "" -m 64 -serial tcp::4444,server > QEMU waiting for connection on: tcp:0.0.0.0:4444,server > Truncating memory to 64 MiB to fit SDRAM controller limits. > QEMU 0.12.50 monitor - type 'help' for more information > (qemu) info kvm > kvm support: enabled > (qemu) > > So things are getting closer, but there's no output on the telnet screen. > > Doing an "info registers" causes qemu to abort. I believe that's a known bug. > Now, nothing should have changed, but it's crashing at startup: > > root@ebony:~# ./qemu-system-ppcemb -nographic -m 128 -M bamboo -kernel uI > mage.bamboo -L . -append "" -m 64 -serial tcp::4444,server > QEMU waiting for connection on: tcp:0.0.0.0:4444,server > Truncating memory to 64 MiB to fit SDRAM controller limits. I don't think it's related, but there must be a silly bug in ppc4xx_sdram_adjust(). 128MB should require just a single bank in the SDRAM controller. > QEMU 0.12.0 monitor - type 'help' for more information > (qemu) qemu: fatal: Trying to execute code outside RAM or ROM at 0x00000000 > > NIP 00000000 LR 00000000 CTR 00000000 XER 00000000 > MSR 00000000 HID0 00000300 HF 00000000 idx 0 > Segmentatio > > backtrace show the invalid memory address, and the segfault is due to > something happening while printing out the information. If you provide the backtrace, I can see if it looks familiar... -Hollis -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
