xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: PV guest with PCI passthrough crash on Xen 4.8.3 inside KVM when booted through OVMF
Date: Fri, 16 Feb 2018 18:48:35 +0100	[thread overview]
Message-ID: <20180216174835.GJ4302@mail-itl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3781 bytes --]

Hi,

As in the subject, the guest crashes on boot, before kernel output
anything. I've isolated this to the conditions below:
 - PV guest have PCI device assigned (e1000e emulated by QEMU in this case),
   without PCI device it works
 - Xen (in KVM) is started through OVMF; with seabios it works
 - nested HVM is disabled in KVM
 - AMD IOMMU emulation is disabled in KVM; when enabled qemu crashes on
   boot (looks like qemu bug, unrelated to this one)

Version info:
 - KVM host: OpenSUSE 42.3, qemu 2.9.1, ovmf-2017+git1492060560.b6d11d7c46-4.1, AMD
 - Xen host: Xen 4.8.3, dom0: Linux 4.14.13
 - Xen domU: Linux 4.14.13, direct boot

Not sure if relevant, but initially I've tried booting xen.efi /mapbs
/noexitboot and then dom0 kernel crashed saying something about conflict
between e820 and kernel mapping. But now those options are disabled.

The crash message:
(XEN) d1v0 Unhandled invalid opcode fault/trap [#6, ec=0000]
(XEN) domain_crash_sync called from entry.S: fault at ffff82d080218720 entry.o#create_bounce_frame+0x137/0x146
(XEN) Domain 1 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-4.8.3  x86_64  debug=n   Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e033:[<ffffffff826d9156>]
(XEN) RFLAGS: 0000000000000296   EM: 1   CONTEXT: pv guest (d1v0)
(XEN) rax: 0000000000000000   rbx: bdb25197f3daa61a   rcx: 000000000000003f
(XEN) rdx: ffffffff8206f450   rsi: 000000000000003f   rdi: 0000000000000000
(XEN) rbp: ffffffff82203e50   rsp: ffffffff82203d88   r8:  65c74fe852ba23f1
(XEN) r9:  b483505023b6d4a8   r10: c50a553bf60c0435   r11: fb097667f910d8cc
(XEN) r12: 0000000080000000   r13: 0000000000000000   r14: 0000010000000000
(XEN) r15: 000000000007aa00   cr0: 0000000080050033   cr4: 00000000000006e0
(XEN) cr3: 000000002a00a000   cr2: 0000000000000000
(XEN) fsb: 0000000000000000   gsb: ffffffff826a9000   gss: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffffffff82203d88:
(XEN)    000000000000003f fb097667f910d8cc ffffffff826d9156 000000010000e030
(XEN)    0000000000010096 ffffffff82203dc8 000000000000e02b ffffffff826d9156
(XEN)    0add82a0ac2d25fc ffffffff82203e58 0000000001000000 ffffffff00000001
(XEN)    000000007f600000 0000000300000000 0000000019000000 0000000000019000
(XEN)    7ff0ffff82203e68 ffffffff00000017 ffffffff827ef004 0000000000000000
(XEN)    a2cc4720129e68ea 0000000001000000 ffffffff81000000 ffffffff82a66000
(XEN)    ffffffff82203ef8 ffffffff82203e70 ffffffff826e59d6 a76c832b9f537b2a
(XEN)    0000000001000000 ffffffff82203ee8 ffffffff826e13f7 0000000000000000
(XEN)    ffffffff810fbd4d cc49d4ba00000010 ffffffff82203ef8 ffffffff82203eb0
(XEN)    0000000000000000 0000000002a95000 0000000000000000 ec77a7137dd29529
(XEN)    ffffffffffffffff ffffffff82203f54 0000000000000000 0000000000000000
(XEN)    ffffffff82203f38 ffffffff826cd7a6 bb0469b365c5dafd ffffffff82203f20
(XEN)    0000000000000000 8529976ce838b598 ffffffff82203f58 ffffffff82203f54
(XEN)    0000000000000000 0000000000000000 ffffffff82203ff8 ffffffff826db329
(XEN)    00100f4200000000 0000000100000800 000000000789c3f5 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0f00000060c0c748

Any idea where to look?

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

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

             reply	other threads:[~2018-02-16 17:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 17:48 Marek Marczykowski-Górecki [this message]
2018-02-16 17:52 ` PV guest with PCI passthrough crash on Xen 4.8.3 inside KVM when booted through OVMF Andrew Cooper
2018-02-16 18:51   ` Marek Marczykowski-Górecki
2018-02-16 19:02     ` Andrew Cooper
2018-02-16 19:54       ` Marek Marczykowski-Górecki
2018-02-19 17:23         ` Juergen Gross
2018-02-19 17:29           ` Marek Marczykowski-Górecki
2018-02-19 17:46             ` Juergen Gross
2018-02-19 17:49               ` Andrew Cooper
2018-02-16 21:35       ` Rich Persaud
2018-02-19 17:13         ` Roger Pau Monné
2018-02-19 17:30       ` Juergen Gross
2023-11-26 14:51         ` [Xen-devel] " Marek Marczykowski-Górecki
     [not found]           ` <CACHz=ZiWufUenyw_wg+QuK86+gU5RZNkuJNzX9-K1UM5P3m8+Q@mail.gmail.com>
2023-11-27 11:26             ` Marek Marczykowski-Górecki
2023-11-27 15:56               ` Jason Andryuk
2023-11-27 16:05                 ` Juergen Gross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180216174835.GJ4302@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).