Re: [Xen-devel] Bisected Xen-unstable: "Segment register inaccessible for d1v0" when starting HVM guest on intel

["Wu, Feng" <feng.wu@xxxxxxxxx>]

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: Friday, July 04, 2014 2:50 PM
> To: Wu, Feng
> Cc: Andrew Cooper; Sander Eikelenboom; xen-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: RE: Bisected Xen-unstable: "Segment register inaccessible for d1v0"
> when starting HVM guest on intel
> 
> >>> On 04.07.14 at 04:51, <feng.wu@xxxxxxxxx> wrote:
> > I try to reproduce this issue on my side, but I find that the per-VCPU guest
> > runstate shared memory area
> > is not registered by the HVM guest, so in update_runstate_area(), it always
> > returns 1 and bypass the
> > remaining logic. I am wondering how it is registered in your HVM guest, were
> > you running an PVHVM guest
> > or HVM guest with PV drivers, I think which may register this area.
> >
> > Jan, do you have some ideas about this, Thanks a lot!
> 
> You should have clarified what kind of guest(s) you tried. Pv-ops Linux,
> afaict, appears to register these areas not just in PV mode.

I tried two kinds of guests:
1. RHEL 6.5 with its own kernel.
2. I built a 3.11.4 kernel in RHEL 6.5 and boot from this new kernel.

Both the them don't register the 'runstate shared memory area', do I
need to configure something else in .config when building the kernel?

Thanks,
Feng

> 
> Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel