From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.xen@gmail.com>
Subject: Re: XEN) vmx.c:2652:d1 Bad vmexit (reason 31) with Xen
	4.0.1-rc7-pre (cs/ 23029)
Date: Fri, 18 Mar 2011 15:31:32 +0000
Message-ID: <C9A92B54.150A3%keir.xen@gmail.com>
References: <4D831E1A0200007800037343@vpn.id2.novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4D831E1A0200007800037343@vpn.id2.novell.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <JBeulich@novell.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 18/03/2011 07:55, "Jan Beulich" <JBeulich@novell.com> wrote:

>> Exit reason 31 is EXIT_REASON_MSR_READ. I don't see how that error can ever
>> be printed for that exit reason. Could you do a bit of digging and see if
>> you agree? The logic is straightforward enough -- the error comes from a
>> default case in a switch statement, but the switch does explicitly handle
>> EXIT_REASON_MSR_READ. There is also a exit_and_crash label for the default
>> case, but EXIT_REASON_MSR_READ doesn't goto it afaics. So this is a weird
>> and inexplicable bug, to me. :-)
> 
> No, the reason is printed in hex

Grrr! I'll add the '0x' prefix.

 -- Keir

> and thus it's EXIT_REASON_EPT_MISCONFIG,
> which isn't being handled in the switch statement (and I can't see
> how it sensibly could be). But the mere register state is insufficient
> to determine what's wrong.