2010/10/11 Rahul Ramasubramanian <ramasubramanian.rahul at gmail.com>
> Hi
> I am trying to boot the guest kernel on the android emulator using the adb
> shell as mentioned in the wiki.
> After all the builds when i run the command
> /data/qemu-system-arm -kernel /data/zImage.integrator -initrd
> /data/arm_root.img --enable-kvm -nographic -append "console=ttyAMA0 debug"
> the system freezes after uncompressing the kernel
>
When you say "system freezes" what exactly is happening? The guest never
responds, the whole emulator is unresponsive or ...?
>
> # /data/qemu-system-arm -kernel /data/zImage.integrator -initrd
> /data/arm_root.img --enable-kvm -nographic -append "console=ttyAMA0 debug"
> Uncompressing
> Linux..........................................................................
> done, booting the kernel.
>
see the point below about further logging
>
>
> I am using the following sources
> Android Cupcake (1.5 version)
> android-extra (master)
> linux-android-common (android-goldfish-2.6.27-kvm-upstream_qemu)
> linux-guest (v2.6.17-lpv)
> qemu ( armkvm-upstream)
>
> Has someone come across this problem before.
> Also , curiously , I don't get the home screen in the android emulator ( it
> just displays the Android animation and stops there).
>
After which changes do you observe this behavior. Try using the stock
android kernel. If that helps, then you probably have an incorrect kernel
config.
> I am not getting any kvm related logs in the host kernel either
>
host kernel log entries are made using simple printk statements you can
usually see them in the shell from where you execute the emulator. I think
there's an option called --show-kernel or something like that. To verify,
place a simple printk(KERN_ERR "hello, do you see me\n"); call somewhere in
a function you know executes. Perhaps make sure you see debug messages in
the kernel as well "cat 8 > /proc/sys/kernel/printk"
>
> I would appreciate if some one could point out what i am missing here.
> Also, is there a way to turn on the verbose logs in the guest and host
> kernel so that i can try to see where it is getting stuck.
>
yes, try using these bootargs to the kernel instead when running the guest:
-append "console=ttyAMA0 earlyprintk debug initcall_debug"
For more low-level stuff (or before your ttys have been initialized, you can
place calls like these in the guest kernel:
asm volatile("mov r0, #3; swi 0xdead": : : "r0");
and then change #3 to #4, #5 etc. and catch that command in handle_swi in
arch/arm/kvm/arm.c on the host kernel and print the numbers. (In fact you
can implement your own low-level-hyper-printk mechanism this way if you want
:))
> Thanks and Regards
> Rahul
>
Good luck!
>
>
>
>
>
> _______________________________________________
> Android-virt mailing list
> Android-virt at lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/android-virt
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.cs.columbia.edu/pipermail/android-virt/attachments/20101011/88e7edd4/attachment.html
