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

["Jan Beulich" <JBeulich@xxxxxxxxxx>]

>>> On 18.03.11 at 00:27, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
> 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=0.0.0.0,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. :-)

No, the reason is printed in hex 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.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel