Re: [Xen-devel] lastest xen unstable crash

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 10.04.12 at 13:08, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
> In any case, a fundamental question is whether your CPU has
> XSAVE support in the first place, and whether kernel and
> hypervisor disagree about that for some reason. Could you
> for that purpose post /proc/cpuinfo contents from when running
> a native kernel?

Just realized that this question is answered by the log you provided:

(XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7

so indeed the fastest approach (short of someone seeing something
obviously wrong with the code) appears to be to add some tracing to
the CR4 handling (pv_guest_cr4_fixup() and the XSETBV handling in
emulate_privileged_op()), particularly also because the register dump
indicates that the relevant bit was not set in CR4 at the point where
the XSETBV faulted.

Jan


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