[I re-titled this for posterity, since it does turn out to be somewhat raspberry-pi centric]
I'd like to try QEMU as an alternative to cross-compiling. I'm using v. 1.0.1 on fedora 17 [later: same results with 1.6 built from source], the guest image is for arm11. I'm invoking:
qemu-system-arm -cpu arm1176 -m 256 -kernel [kernel] -append "root=/dev/sda" -hda [fs.img] -M versatilepb -D log.txt
This produces no output and pops up a blank window. I can
ctrl-alt-2 to get the "qemu monitor" prompt, but I have no idea how to use this to tell me something about the state.
I am absolutely positive the kernel and the fs image are valid, as they were taken together from the actual system. I have also tried publicly available images and kernels using instructions available on-line for the device -- this is where I got the basics of the invocation line. I'm familiar with the creation and use of raw file system images generally.
The emulated system is from a raspberry pi, and there's a long thread of people mostly describing success with qemu (although as mentioned I cannot duplicate their results). However, this is NOT a linux or rpi related question, it's a question (or three) about qemu:
Can QEMU comment at all about the state of the emulator? Is there any way to get it to report something -- anything -- success -- failure -- events -- anything? Note that it does not even create "log.txt", specified with the
-Doption, regardless of whether I 'quit' via the monitor prompt or just kill the process.
Does the fact that it completely maxes out one processor indicate anything? I presume it should not be doing that.
Can the monitor shell be used to debug this kind of problem?
I notice that if I use
qemu-system-x86_64 -kernel [hostkernel] the emulator window comes up and shows the output of a kernel booting, so the blank window with
-arm implies this is a non-starter. I'd just like to try and find out why.