[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Test results on Unisys ES7000 64x 256gbusingunstablec/s 16693 on 3.2.0 Release Candidate

>(XEN) traps.c:414:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0
>(XEN) domain_crash_sync called from entry.S
>(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
>(XEN) ----[ Xen-3.3-unstable  x86_64  debug=y  Not tainted ]----
>(XEN) CPU:    0
>(XEN) RIP:    e033:[<ffffffff804fe6f4>]
>(XEN) RFLAGS: 0000000000000282   CONTEXT: guest
>(XEN) rax: 00000000ffffffea   rbx: ffffffffc0125000   rcx:
>(XEN) rdx: 00000000deadbeef   rsi: 00000000deadbeef   rdi:
>(XEN) rbp: ffffffffa0582000   rsp: ffffffff804ebe78   r8:
>(XEN) r9:  0000000000000000   r10: 00000000deadbeef   r11:
>(XEN) r12: ffffffff80205000   r13: 0000003f14537000   r14:
>(XEN) r15: ffffffff80205000   cr0: 000000008005003b   cr4:
>(XEN) cr3: 0000000480201000   cr2: 0000000000000000
>(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
>(XEN) Guest stack trace from rsp=ffffffff804ebe78:

This looks like a failed hypercall (and a BUG() following it), but without
having the kernel binary it's impossible to tell which one. You should
be able to find out, though. With that information, if it doesn't directly
provide a clue, it should then be possible to instrument the respective
hypercall handler to find out what's going wrong.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.