On 10/20/2009 05:57 PM, Chris Lalancette wrote:
Nikola Ciprich wrote:
Hi,
maybe it's stupid question, but is this available also when qemu/kvm
is started using libvirt& stuff? I think it uses monitor so it's
inaccessible for user no?
Yes and no. The monitor is inaccessible when using libvirt, but I totally
forgot that qemu dumps the register state to stderr before abort()'ing on an
unknown vm exit. Libvirt takes the output from stderr and stores it in
/var/log/libvirt/qemu/<guestname>. So you would still be able to see this
output when using libvirt.
We've dropped the stderr part (IIRC), but nothing prevents libvirt from
accessing the register state and providing it to the user.
There's also the multiple monitor support which can be used for
debugging. Finally, you can connect with gdb (need to dynamically start
the gdb server via the monitor, again needs libvirt support).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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
