From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Lalancette Subject: Re: [PATCH] Print Guest VMCS state on vmexit failure Date: Tue, 20 Oct 2009 10:42:24 +0200 Message-ID: <4ADD77F0.6010102@redhat.com> References: <1256025045-4972-1-git-send-email-clalance@redhat.com> <4ADD70CB.10109@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:46598 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751301AbZJTImW (ORCPT ); Tue, 20 Oct 2009 04:42:22 -0400 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9K8gRWw024302 for ; Tue, 20 Oct 2009 04:42:27 -0400 In-Reply-To: <4ADD70CB.10109@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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