Did you use a self-compiled guest AOSP image for the user space utilities that crash or the Arndale android dist.? Can you see if you can grab a pre-compiled one from somewhere? I have a feeling there's something wrong with the user space build... On Tue, Apr 23, 2013 at 5:07 PM, Howard Mao <zhehao.mao@xxxxxxxxx> wrote: > I have VFP support enabled in the kernel config already. I will try using > Alexander's kernel and qemu and see if that works. Thanks to both of you for > your help. > > > On Fri, Apr 19, 2013 at 5:36 AM, Marc Zyngier <marc.zyngier@xxxxxxx> wrote: >> >> On 19/04/13 03:33, Howard Mao wrote: >> > Christoffer and I are attempting to boot an Android image on a Linux 3.9 >> > kernel with KVM-ARM enabled in QEMU, but on boot we keep getting a >> > kernel panic complaining about an illegal instruction in init. >> > >> > init (1): undefined instruction: pc=00021a26 >> > Code: b5070000 46692001 ed3cf7f5 9b004a0d (0a01ed9d) >> > Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 >> > >> > [<8001fe24>] (unwind_backtrace+0x0/0xf8) from [<803b4a5c>] >> > (panic+0x90/0x1e4) >> > [<803b4a5c>] (panic+0x90/0x1e4) from [<8002fe3c>] (do_exit+0x848/0x8b0) >> > [<8002fe3c>] (do_exit+0x848/0x8b0) from [<80030008>] >> > (do_group_exit+0x3c/0xc4) >> > [<80030008>] (do_group_exit+0x3c/0xc4) from [<8003a398>] >> > (get_signal_to_deliver+0x170/0x56c) >> > [<8003a398>] (get_signal_to_deliver+0x170/0x56c) from [<8001c82c>] >> > (do_signal+0xf0/0x3fc) >> > [<8001c82c>] (do_signal+0xf0/0x3fc) from [<8001ce6c>] >> > (do_work_pending+0x68/0xa8) >> > [<8001ce6c>] (do_work_pending+0x68/0xa8) from [<80019900>] >> > (work_pending+0xc/0x20) >> > >> > Has anyone seen something like this before when running Android in QEMU? >> > >> > We are using the kernel >> > from https://github.com/columbia/linux-kvm-arm/tree/arndale-kvm-3.9-rc2 >> > QEMU from https://github.com/columbia/qemu/tree/kvm-arm-virtio >> > Android from http://source.android.com/source/downloading.html >> > >> > This has been tested on an Arndale board with QEMU-KVM and QEMU-TCG and >> > on an x86_64 machine with QEMU-TCG. All three platforms give the same >> > error. >> >> This last sentence would imply that something is wrong in your Android >> build, and has very little to do with KVM. >> >> If you look at the failing instruction, it disassemble as >> VLDR s0, [sp, #4] >> >> My guess is that your guest kernel doesn't have VFP support enabled, >> hence trapping on an UNDEF. >> >> M. >> -- >> Jazz is not dead. It just smells funny... >> > > > _______________________________________________ > kvmarm mailing list > kvmarm@xxxxxxxxxxxxxxxxxxxxx > https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
