>>> On 11.04.18 at 17:03, <o...@aepfle.de> wrote:
> On Wed, Apr 11, Olaf Hering wrote:
> 
>> On Wed, Apr 11, Dario Faggioli wrote:
>> 
>> > Olaf, can you give it a try? It should be fine to run it on top of the
>> > last debug patch (the one that produced this crash).
>> 
>> Yes, with both changes it did >4k iterations already. Thanks.
> 
> That was with sched=credit2, sorry for that.
> Now with just that second patch I got this after a few iterations, in 
> __vmread().
> We have seen such crashes a few times with 4.7 already.

And till now I had assumed we've taken care of them with earlier
fixes (all 4.7 reports were with old packages, like 4.7.2 based
ones). Can you repro this with a debug hypervisor (so we can
both trust the stack trace and know whether any earlier
assertion would trigger)?

Is this also tied to those frequent affinity changes? Are there
multiple guests, or is there any non-default activity (like last time
such an issue was found to be triggered by a guest being
destroyed in parallel)?

Kevin, Jun, I'm adding you early here as it would be really nice if
this time round we could get some help from you (being the VMX
maintainers after all).

Jan

> (XEN) Xen BUG at ...0f8ba84a5/non-dbg/xen/include/asm/hvm/vmx/vmx.h:390
> (XEN) ----[ Xen-4.11.20180410T125709.50f8ba84a5-6.bug1087289_411  x86_64  
> debug=n   Not tainted ]----
> (XEN) CPU:    71
> (XEN) RIP:    e008:[<ffff82d08030aa55>] 
> vmx.c#arch/x86/hvm/vmx/vmx.o.unlikely+0/0x15b
> (XEN) RFLAGS: 0000000000010203   CONTEXT: hypervisor (d16v0)
> (XEN) rax: 0000000000004824   rbx: ffff83007ba44000   rcx: ffffffffffffef76
> (XEN) rdx: ffff830e7aa77fff   rsi: 000000000000f305   rdi: ffff83007ba44000
> (XEN) rbp: 000000000000f305   rsp: ffff830e7aa77e60   r8:  0000000015c23047
> (XEN) r9:  000004489c4a4a69   r10: 000001b7ca057c00   r11: 0000000000000000
> (XEN) r12: 000000000000f305   r13: 0000000000004016   r14: ffff830779e92180
> (XEN) r15: 00000000ffffffff   cr0: 000000008005003b   cr4: 00000000001526e0
> (XEN) cr3: 000000067083a000   cr2: 00007fedb9f6c000
> (XEN) fsb: 0000000000000000   gsb: 0000000000000000   gss: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen code around <ffff82d08030aa55> 
> (vmx.c#arch/x86/hvm/vmx/vmx.o.unlikely):
> (XEN)  44 24 0c e9 82 fd ff ff <0f> 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 
> 0b
> (XEN) Xen stack trace from rsp=ffff830e7aa77e60:
> (XEN)    ffff82d0802e1442 ffff83007ba44000 000000000000f305 000000000000f305
> (XEN)    ffff82d0802ff477 ffff82d08030f9ab 000000f37aa77ef8 ffffffffffffffff
> (XEN)    ffff830e7aa77fff ffff82d080933c00 ffff830779e92180 ffff82d08026d870
> (XEN)    ffff83007ba44000 ffff83007ba44000 ffff830779e92188 000001b7c8fec61b
> (XEN)    ffff830779e92180 ffff82d08094a480 ffff82d08030f9e7 ffffffff81c00000
> (XEN)    ffffffff81c00000 ffffffff81c00000 0000000000000000 0000000000000000
> (XEN)    ffffffff81d4c180 0000000000000400 0000000000000400 0000000000000000
> (XEN)    0000000000000000 ffffffff81020e50 0000000000000000 0000000000000000
> (XEN)    0000000000000000 0000000000000000 000000fc00000000 ffffffff81060182
> (XEN)    0000000000000000 0000000000000246 ffffffff81c03f00 0000000000000000
> (XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    0000000000000047 ffff83007ba44000 00000036f9533080 00000000001526e0
> (XEN)    0000000000000000 0000000779e90000 0000040000000000 0000000000000000
> (XEN) Xen call trace:
> (XEN)    [<ffff82d08030aa55>] vmx.c#arch/x86/hvm/vmx/vmx.o.unlikely+0/0x15b
> (XEN)    [<ffff82d0802e1442>] hvm_interrupt_blocked+0x82/0xd0
> (XEN)    [<ffff82d0802ff477>] vmx_intr_assist+0x137/0x490
> (XEN)    [<ffff82d08030f9ab>] vmx_asm_vmexit_handler+0xab/0x240
> (XEN)    [<ffff82d08026d870>] domain.c#vcpu_kick_softirq+0/0x10
> (XEN)    [<ffff82d08030f9e7>] vmx_asm_vmexit_handler+0xe7/0x240
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 71:
> (XEN) Xen BUG at ...0f8ba84a5/non-dbg/xen/include/asm/hvm/vmx/vmx.h:390
> (XEN) ****************************************
> 
> 
> Olaf



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to