>>> On 03.08.16 at 15:24, <kevin.ma...@gdata.de> wrote: > I got around to take a closer look at the crash dump today. > > tl;dr: > You were right, vmx_vmenter_helper is not called at all in the call stack. > The real reason behind the [<ffff82d0801fd23a>] > vmx_vmenter_helper+0x27e/0x30a > should be a failed > __vmwrite(HOST_CR0, v->arch.hvm_vmx.host_cr0); in static void > vmx_fpu_leave(struct vcpu *v).
Ah - that's what you get for not using most recent code, and what I get for not considering the effect of you being on 4.6.x. In any event - the call stack is then fine, and you'll want to figure out which bit(s) of the new CR0 value are in conflict with the rest of the active VMCS. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
