On 17.12.2009, at 08:21, Hollis Blanchard wrote: > I don't understand why you don't have console. If you did, you could > use the initcall_debug kernel parameter. > > Aside from that, find __log_buf in System.map, then dump that chunk of > memory using qemu's monitor interface. That should at least give you a > backtrace from the panic. If it's an initcall indirect function call, > the initcall_debug parameter will give you some clues. Another thing that's really been useful to me there was the gdb interface. Qemu has a pretty good gdb stub and for KVM support all you need to do is implement the register synchronization. That way you can just 'bt' and see your way through the guest kernel. If you have the debug symbols of that kernel around, you even get all the great debug magic you could possibly get ;-). Alex
