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: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
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: Thu, 17 Mar 2011 23:27:01 +0000
Delivery-date: Thu, 17 Mar 2011 16:27:51 -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:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=sBpb0niDf8shJOVKQauM1hxtsWbiM/QkNl7mA73JqX8=; b=dXrGaxYpsEvPEhNbzqNcWAwk4YQUR0d2SimNCh5T8sHZJlaTYidEdvnfFVZyD5PYkL ZS7uOxRrvoo8dZPfhaJNSNpVSoQ9kUyusHiS7S6vaGhzqRpJiLCaUr+b7r/DJlamsR5W MZHn735m331Ioq/rGcQlltz8Ykpuao/K1K6UM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=M9Hyi04u9qYN3xn4LPGstIoNgJQUQ2MV6MlA6+wukSAX14g8WbntEBKo1M+Br/+/U1 8/krWwKSV5QExhzjl9E7YqzJqpIbCzcCtbdD2GKfct7usCNgm/CN685b252juhHkLl7Y DqIzT7/FMR3Tr8RsyXn6DzXRl5se6OBuAr/SQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110317202605.GA25684@xxxxxxxxxxxx>
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: Acvk+tEG2xs8l+JqLEScdAuG2rqd7g==
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 17/03/2011 20:26, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:

> The guest config is quite simple:
> kernel = "/usr/lib/xen/boot/hvmloader"
> builder='hvm'
> memory=1024
> #maxmem=1024
> maxvcpus = 4
> serial='pty'
> vcpus = 2
> disk = [ 'file:/mnt/lab/latest/root_image.iso,hdc:cdrom,r']
> boot="dn"
> vif = [ 'type=ioemu,model=e1000,mac=00:0F:4B:00:00:71, bridge=switch' ]
> vfb = [ 'vnc=1, vnclisten=,vncunused=1']
> And this is what shows up after I do 'xm create hvm.xm' (or xl create hvm.xm).
>   alloc irq_desc for 4223 on node -1
>   alloc kstat_irqs on node -1
> (XEN) vmx.c:2652:d1 Bad vmexit (reason 31)

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

 -- Keir

Xen-devel mailing list