From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Chris Lalancette <clalance@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz
Subject: Re: [PATCH] Print Guest VMCS state on vmexit failure
Date: Tue, 20 Oct 2009 10:55:22 +0200 [thread overview]
Message-ID: <20091020085522.GA6416@develbox.linuxbox.cz> (raw)
In-Reply-To: <4ADD77F0.6010102@redhat.com>
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?
n.
On Tue, Oct 20, 2009 at 10:42:24AM +0200, Chris Lalancette wrote:
> Avi Kivity wrote:
> > On 10/20/2009 04:50 PM, Chris Lalancette wrote:
> >> If we fail to handle a VMEXIT for some reason, print out a lot
> >> more debugging information about the state of the GUEST VMCS
> >> area. This does not fix a bug, but helps a lot when trying to
> >> track down the cause of a VMEXIT/VMENTRY failure.
> >>
> >
> > register state can just as easily be examined in the qemu monitor.
> >
>
> Ah, true. OK, forget this patch.
>
> --
> Chris Lalancette
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2009-10-20 8:55 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 [this message]
2009-10-20 8:57 ` Chris Lalancette
2009-10-20 9:08 ` Avi Kivity
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=20091020085522.GA6416@develbox.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=avi@redhat.com \
--cc=clalance@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.