This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] XEN) vmx.c:2652:d1 Bad vmexit (reason 31) with Xen 4.0.1

To: Jan Beulich <JBeulich@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] XEN) vmx.c:2652:d1 Bad vmexit (reason 31) with Xen 4.0.1-rc7-pre (cs/ 23029)
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Fri, 18 Mar 2011 15:31:32 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 18 Mar 2011 08:32:15 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:cc:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=ElOHwk+Q6ofi3VPcO8xZjs/p6GoBXCl65HhX8NsCqZg=; b=S26A06hndsE7IXfLGvUtrt+xA+fR/wtnIwNMS19nOtvL8Mi2FTXEXGkBEF/ZdL5pKb YTy4qiMCFu129jNnHqdQXfei1zpSHakIlwioRQfNXPniXBuVN8K6LY8k0fMbqQuRTv09 k8t+uSvHKWJHtGoRImaBbZMuV4YI6kH4tas3U=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=lp9leO28SHVAaotGYV0JCGu60CVE6BrLRrODjU3S1Ixp2bTdijtHwYwC23BMGkxld0 FxtrnKcnTJSoOm20oT9nNuVY3U15xj9EntZMSWUvwUOSHtN8xK6cECgfoLGesknY87U4 oHY6rGvcdfLyQlOwMIseRB/A7L29HJwdK/ZVU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D831E1A0200007800037343@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvlgY7UbXHme12qLECppRLZwrwSOA==
Thread-topic: [Xen-devel] XEN) vmx.c:2652:d1 Bad vmexit (reason 31) with Xen 4.0.1-rc7-pre (cs/ 23029)
User-agent: Microsoft-Entourage/
On 18/03/2011 07:55, "Jan Beulich" <JBeulich@xxxxxxxxxx> 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

> 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.

Xen-devel mailing list