This appears to be user confusion.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1011142
Title:
Arm emulation do a crash
Status in QEMU:
Invali
Hello, I have succefull run debian raspberry pi under qemu.
Then I try do like under my x86, mount -t proc none proc,..., chroot
/mnt/gentoo /bin/bash, ... -> illegal instruction.
Then I try with boot directly from the gentoo's part -> lot of illegal
instruction, I have used like say on the web:
On 10 June 2012 18:52, BRULE Herman <1011...@bugs.launchpad.net> wrote:
> Because it stop on:
> Program received signal SIG38, Real-time event 38.
> [Switching to Thread 0x71125700 (LWP 32348)]
> tcg_qemu_tb_exec (cpustate=, tb_ptr=0x400016b3 "\025\b") at
> /var/tmp-disk/portage/app-emulation/
I have found the bug, gentoo "qemu-kvm" is not "qemu" package, and with
qemu packages all work. Now I don't know where repport the bug...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1011142
Title:
Just basic support, that's mean: no crash, and minimal system in console
boot (all device emulated by QEMU is already supported). For me the
crash, and mainly this cpu seam be supported by QEMU, just have the
instruction bugged.
--
You received this bug notification because you are a member of qe
The missing emulation of Raspberry PI hardware is not a QEMU bug.
Anybody is free to add this emulation or to support others to do the job.
It won't be easy because the RPi hardware is only partially documented,
and the RPi system uses closed source drivers for video.
If nobody objects, I suggest
Then the correct gdb command provide:
#0 tcg_qemu_tb_exec (cpustate=, tb_ptr=0x0) at
/var/tmp-disk/portage/app-emulation/qemu-kvm-1.0.1-r1/work/qemu-kvm-1.0.1/tci.c:444
#1 0x7f6ced51393d in cpu_arm_exec (env=0x7f6cee66c3d0) at
/var/tmp-disk/portage/app-emulation/qemu-kvm-1.0.1-r1/work/qemu-
Obviously you compiled QEMU using the experimental TCI (TCG interpreter).
That's not wrong (for debugging some kinds of crashes it is even useful),
but it's slow.
You also called gdb with qemu-system-x86_64, but the core was from qemu-
system-arm.
Which kernel did you use? zImage or kernel-raspto
Because it stop on:
Program received signal SIG38, Real-time event 38.
[Switching to Thread 0x71125700 (LWP 32348)]
tcg_qemu_tb_exec (cpustate=, tb_ptr=0x400016b3 "\025\b") at
/var/tmp-disk/portage/app-emulation/qemu-kvm-1.0.1-r1/work/qemu-kvm-1.0.1/tci.c:442
442
/var/tmp-disk/portage/app
