From: Avi Kivity <avi@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: Nikola Ciprich <extmaillist@linuxbox.cz>,
kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz
Subject: Re: [PATCH] Print Guest VMCS state on vmexit failure
Date: Tue, 20 Oct 2009 18:08:57 +0900 [thread overview]
Message-ID: <4ADD7E29.1070100@redhat.com> (raw)
In-Reply-To: <4ADD7B83.2050603@redhat.com>
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.
prev parent reply other threads:[~2009-10-20 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 7:50 [PATCH] Print Guest VMCS state on vmexit failure Chris Lalancette
2009-10-20 7:57 ` Gleb Natapov
2009-10-20 8:01 ` Chris Lalancette
2009-10-20 8:11 ` Avi Kivity
2009-10-20 8:42 ` Chris Lalancette
2009-10-20 8:55 ` Nikola Ciprich
2009-10-20 8:57 ` Chris Lalancette
2009-10-20 9:08 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ADD7E29.1070100@redhat.com \
--to=avi@redhat.com \
--cc=clalance@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).