Am 24.10.2011 13:29, schrieb Chris Webb: > Kevin Wolf <kwolf@xxxxxxxxxx> writes: > >> In qemu 1.0 we'll have an extended 'info status' that includes the stop >> reason, but 0.14 doesn't have this yet (was committed to git master only >> recently). > > Right, okay. I might take a look at cherry-picking and back-porting that to > our version of qemu-kvm if it's not too entangled with other changes. It > would be very useful in these situations. I'm afraid that it depends on many other changes, but you can try. > >> If you attach a QMP monitor (see QMP/README, don't forget to send the >> capabilities command, it's part of creating the connection) you will >> receive messages for I/O errors, though. > > Thanks. I don't think I can do this with an already-running qemu-kvm that's > in a stopped state can I, only with a new qemu-kvm invocation and wait to > try to catch the problem again? Good point... The only other thing that I can think of would be attaching gdb and setting a breakpoint in vm_stop() or something. Kevin -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
