From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikola Ciprich Subject: Re: [PATCH] Print Guest VMCS state on vmexit failure Date: Tue, 20 Oct 2009 10:55:22 +0200 Message-ID: <20091020085522.GA6416@develbox.linuxbox.cz> References: <1256025045-4972-1-git-send-email-clalance@redhat.com> <4ADD70CB.10109@redhat.com> <4ADD77F0.6010102@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz To: Chris Lalancette Return-path: Received: from gw3.lbox.cz ([62.245.111.133]:41959 "EHLO develbox.linuxbox.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751335AbZJTIzF (ORCPT ); Tue, 20 Oct 2009 04:55:05 -0400 Content-Disposition: inline In-Reply-To: <4ADD77F0.6010102@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 -------------------------------------