Hello, This bug is linked with: https://bugs.launchpad.net/qemu/+bug/1011142 I need qemu 1.0.1 to have correct arm emulation, to emulate and compil for raspberry pi. I need too qemu-kvm because qemu do crash windows 7: https://bugs.launchpad.net/qemu/+bug/1012023 The most use full to me, it's have both. Can you enable multi-slot if no have architecture conflict (one qemu for some architecture, qemu-kvm for other architecture). Thanks.
Can you elaborate why you can't use qemu-kvm with ARM support? While I don't have a Pi I do use qemu-kvm with ARM support for several other ARM devices I have and it works fine.
Because it have bugged [QUOTE]experimental TCI (TCG interpreter).[/QUOTE] That's do here crash with official OS (crash after the kernel initialization). zImage found to support qemu with raspberry pi (with qemu all work).
(In reply to comment #2) > Because it have bugged > [QUOTE]experimental TCI (TCG interpreter).[/QUOTE] > That's do here crash with official OS (crash after the kernel > initialization). zImage found to support qemu with raspberry pi (with qemu > all work). That code is identical from qemu, in the qemu-kvm release. There's nothing patched or modified with it. So it should work the same.
But it not work the same... It's why qemu + qemu-kvm can be useful, to have access to both application (for bug or features).
I really don't see how you are saying its not working the same. Upstream is telling you that raspberry pi support does not exist in qemu. The qemu-kvm package is built with extra debugging that is telling you details about what isn't implemented and why it's failing. The qemu package does not have this on and as a result you get a silent crash. Based on his silence you are assuming that qemu is working better and therefore we should split out the packages. The real solution is to add the missing support to qemu.
(In reply to comment #5) > I really don't see how you are saying its not working the same. Upstream is > telling you that raspberry pi support does not exist in qemu. The qemu-kvm > package is built with extra debugging that is telling you details about what > isn't implemented and why it's failing. The qemu package does not have this > on and as a result you get a silent crash. Based on his silence you are > assuming that qemu is working better and therefore we should split out the > packages. > > The real solution is to add the missing support to qemu. Ok, thanks for your clear explain. It should be that's.
