Re: [Xen-devel] [BUG] L2 Guest on hyper-v causes domain_crash

[Steven Krikstone <skrikstone@xxxxxxxxx>]

On Wed, Mar 26, 2014 at 3:22 AM, Zhang, Yang Z <yang.z.zhang@xxxxxxxxx> wrote:

Steven Krikstone wrote on 2014-03-26:

> Hello,
>
> Running a FreeBSD L2 guest in Hyper-V on Windows Server 2012 R2 as the
> L1 causes the following guest domain crash.
>
> ### Setup: Intel server running Ubuntu 13.10 with Xen 4.4.1pre
> (git:staging-4.4:babcef3 with 1 patch) The Ubuntu server is a stock
> install with just the necessary packages installed to run Xen.
> Windows Server 2012 R2 is a stock install with the Hyper-V role added.
> The following patch from:
> http://lists.xen.org/archives/html/xen-devel/2014-02/msg01071.html was
> required or else Windows Server VM would hang at the boot splash screen.
>
> If I set "nestedhvm=0" Server 2012R2 runs without issue (minus a
> working Hyper-v role).
>
> Let me know if you need further logs or traces provided.
>
> Thanks,
>
> -steve
>
> ### xl dmesg [..many L0 PIO lines snipped..] (XEN) L0 PIO 01f7 (XEN)
> L0 PIO c220 (XEN) L0 PIO c222 (XEN) L0 PIO c222 (XEN) L0 PIO c220
> (XEN) L0 PIO c222 (XEN) L0 PIO 01f7 (XEN) L0 PIO 01f7 (XEN) L0 PIO
> c203 (XEN) L0 PIO c205 (XEN) L0 PIO c203 (XEN) L0 PIO c205 (XEN) L0
> PIO c207 (XEN) L0 PIO c211 (XEN) L0 PIO c213 (XEN) L0 PIO c205 (XEN)
> L0 PIO c207 (XEN)
> vvmx.c:2477:d3 Unknown nested vmexit reason 80000021. (XEN) Failed vm
> entry (exit reason 0x80000021) caused by invalid guest state (0).
> (XEN)
> ************* VMCS Area ************** (XEN) *** Guest State *** (XEN)
> CR0: actual=0x0000000080010031, shadow=0x0000000080050031,
> gh_mask=ffffffffffffffff (XEN) CR4: actual=0x00000000001526f8,
> shadow=0x00000000001506f8, gh_mask=ffffffffffffffff (XEN) CR3:
> actual=0x00000000001a7000, target_count=0 (XEN)
> target0=0000000000000000, target1=0000000000000000 (XEN)
> target2=0000000000000000, target3=0000000000000000 (XEN) RSP =
> 0xffffd00020b3c890 (0xffffd00020b3c890)  RIP = 0xfffff80320f0c0ab
> (0xfffff80320f0c0ab) (XEN) RFLAGS=0x0000000000000046
> (0x0000000000000046)  DR7 = 0x0000000000000400 (XEN) Sysenter
> RSP=0000000000000000 CS:RIP=0000:0000000000000000 (XEN) CS:
> sel=0x0010, attr=0x0209b, limit=0x00000000, base=0x0000000000000000 (XEN) DS:
> sel=0x002b, attr=0x0c0f3, limit=0xffffffff, base=0x0000000000000000
> (XEN) SS: sel=0x0018, attr=0x0c093, limit=0xffffffff,
> base=0x0000000000000000 (XEN) ES: sel=0x002b, attr=0x0c0f3,
> limit=0xffffffff, base=0x0000000000000000 (XEN) FS: sel=0x0053,
> attr=0x040f3, limit=0x0000fc00, base=0x00000000ff9ce000 (XEN) GS:
> sel=0x002b, attr=0x0c0f3, limit=0xffffffff, base=0xffffd00020b12000
> (XEN) GDTR:                           limit=0x0000007f,
> base=0xffffd00020b1f040 (XEN) LDTR: sel=0x0000, attr=0x1c000,
> limit=0xffffffff, base=0x0000000000000000 (XEN) IDTR:
>        limit=0x00000fff, base=0xffffd00020b1f0c0 (XEN) TR: sel=0x0040,
> attr=0x0008b, limit=0x00000067, base=0xffffd00020b18080 (XEN) Guest
> PAT = 0x0000050100070406 (XEN) TSC Offset = fffffefc546de420 (XEN)
> DebugCtl=0000000000000000 DebugExceptions=0000000000000000 (XEN)
> Interruptibility=0008 ActivityState=0000

Seems the virtual NMI handling for nested is not correct: blocking by NMI is set, but trying to inject a NMI to guest.

Best regards,
Yang

I am more than willing to test any patches you may have.  I am also leaving this testbed setup in case you or others need further logs, debugs run, etc.

Thanks,

-steve

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