From: "Jan Beulich" <JBeulich@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xen.org, PGNet Dev <pgnet.dev@gmail.com>,
wei.liu2@citrix.com, roger.pau@citrix.com
Subject: Re: Clarifying PVH mode requirements
Date: Mon, 01 Feb 2016 09:56:05 -0700 [thread overview]
Message-ID: <56AF9C3502000078000CD238@prv-mh.provo.novell.com> (raw)
In-Reply-To: <56AF71AD.8010100@oracle.com>
>>> On 01.02.16 at 15:54, <boris.ostrovsky@oracle.com> wrote:
> On 02/01/2016 08:38 AM, PGNet Dev wrote:
>>
>> Loading Xen 4.6.0_08-405 with Linux 4.4.0-8.g9f68b90-default
>> ...Loading Xen 4.6.0_08-405 with Linux 4.4.0-8.g9f68b90-default ...
>>
>> /EndEntire
>> /EndEntire
>> file path: file path:
>>
> /ACPI(a0341d0,0)/ACPI(a0341d0,0)/PCI(1,1c)/PCI(1,1c)/PCI(0,0)/PCI(0,0)/PCI(0,
> 1)/PCI(0,1)/PCI(0,0)/PCI(0,0)/HardwareVendor
>> (cf31fac5-c24e-11d2-85f3-00a0c93ec93b)[1:
>> /HardwareVendor(cf31fac5-c24e-11d2-85f3-00a0c93ec93b)[1: 88 88
>> ]]/HD(2,1000,96000,c5cc9661271ee648
>> ,2,2)/HD(2,1000,96000,c5cc9661271ee648,2,2)/File(\EFI\OPENSUSE)
>>
> /File(\EFI\OPENSUSE)/File(xen-4.6.0_08-405.efi)/File(xen-4.6.0_08-405.efi)/EndEnt
> ire
>>
>> /EndEntire
>> Xen 4.6.0_08-405 (c/s ) EFI loader
>> Using configuration file 'xen-4.6.0_08-405.cfg'
>> vmlinuz-4.4.0-8.g9f68b90-default: 0x000000008bf22000-0x000000008c507000
>> initrd-4.4.0-8.g9f68b90-default: 0x000000008afbc000-0x000000008bf21da8
>> 0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x92a26018
>> 0x0000:0x03:0x00.0x0: ROM: 0x8000 bytes at 0x92a1d018
>> 0x0000:0x0f:0x00.0x0: ROM: 0x10800 bytes at 0x929fc018
>> __ __ _ _ __ ___ ___ ___ _ _ ___ ____
>> \ \/ /___ _ __ | || | / /_ / _ \ / _ \ ( _ ) | || | / _ \| ___|
>> \ // _ \ '_ \ | || |_| '_ \| | | | | | | |/ _ \ __| || |_| | | |___ \
>> / \ __/ | | | |__ _| (_) | |_| | | |_| | (_) |__|__ _| |_|
>> |___) |
>> /_/\_\___|_| |_| |_|(_)___(_)___/___\___/ \___/ |_| \___/|____/
>> |_____|
>> (XEN) Xen version 4.6.0_08-405 (abuild@suse.de) (gcc (SUSE Linux)
>> 4.8.5) debug=n Wed Jan 27 15:23:26 UTC 2016
>>
>
> ....
>
>> (XEN) [2016-02-01 05:28:29] d0v0 EPT violation 0x1aa (-w-/r-x) gpa
>> 0x000000f100054c mfn 0xf1000 type 5
>> (XEN) [2016-02-01 05:28:29] d0v0 Walking EPT tables for GFN f1000:
>> (XEN) [2016-02-01 05:28:29] d0v0 epte 800000084510c107
>> (XEN) [2016-02-01 05:28:29] d0v0 epte 800000085b684107
>> (XEN) [2016-02-01 05:28:29] d0v0 epte 8000000844afb107
>> (XEN) [2016-02-01 05:28:29] d0v0 epte 80500000f1000905
>> (XEN) [2016-02-01 05:28:29] d0v0 --- GLA 0xffffc900006a254c
>> (XEN) [2016-02-01 05:28:29] domain_crash called from vmx.c:2685
>> (XEN) [2016-02-01 05:28:29] Domain 0 (vcpu#0) crashed on cpu#0:
>> (XEN) [2016-02-01 05:28:29] ----[ Xen-4.6.0_08-405 x86_64 debug=n
>> Tainted: C ]----
>> (XEN) [2016-02-01 05:28:29] CPU: 0
>> (XEN) [2016-02-01 05:28:29] RIP: 0010:[<ffffffff8142a4ac>]
>> (XEN) [2016-02-01 05:28:29] RFLAGS: 0000000000010246 CONTEXT: hvm
>> guest (d0v0)
>> (XEN) [2016-02-01 05:28:29] rax: 000000000000000d rbx:
>> 00000000f100054c rcx: 000000009e9c4fff
>> (XEN) [2016-02-01 05:28:29] rdx: 0000000000000000 rsi:
>> 0000000000000100 rdi: ffffffff81eaedc0
>> (XEN) [2016-02-01 05:28:29] rbp: ffff880164b57908 rsp:
>> ffff880164b578d8 r8: ffff88016d8c7458
>> (XEN) [2016-02-01 05:28:29] r9: 0000000002400001 r10:
>> 0000000000000000 r11: 0000000000002001
>> (XEN) [2016-02-01 05:28:29] r12: 0000000000000020 r13:
>> ffff88016453aec0 r14: ffffc900006a254c
>> (XEN) [2016-02-01 05:28:29] r15: ffff880164b57a20 cr0:
>> 0000000080050033 cr4: 00000000000406b0
>> (XEN) [2016-02-01 05:28:29] cr3: 0000000001e0b000 cr2: 0000000000000000
>> (XEN) [2016-02-01 05:28:29] ds: 0000 es: 0000 fs: 0000 gs: 0000
>> ss: 0000 cs: 0010
>> (XEN) [2016-02-01 05:28:29] Guest stack trace from rsp=ffff880164b578d8:
>> (XEN) [2016-02-01 05:28:29] Fault while accessing guest memory.
>> (XEN) [2016-02-01 05:28:29] Hardware Dom0 crashed: rebooting machine
>> in 5 seconds.
>
> (+Jan)
>
> This looks very much like it needs backport of 33c19df9a ("x86/PCI:
> intercept accesses to RO MMIO from dom0s in HVM containers") from
> unstable, which fixes PVH regression introduced by 9256f66c1606
> ("x86/PCI: intercept all PV Dom0 MMCFG writes")
I don't really understand: The former was needed to fix an issue
introduced by the latter, but the latter isn't in 4.6 iirc.
Jan
next prev parent reply other threads:[~2016-02-01 16:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 21:27 Clarifying PVH mode requirements PGNet Dev
2016-02-01 3:47 ` PGNet Dev
2016-02-01 10:30 ` Roger Pau Monné
2016-02-01 12:16 ` PGNet Dev
2016-02-01 9:59 ` Wei Liu
2016-02-01 12:23 ` PGNet Dev
2016-02-01 12:29 ` Wei Liu
2016-02-01 12:29 ` Roger Pau Monné
2016-02-01 12:38 ` PGNet Dev
2016-02-01 13:38 ` PGNet Dev
2016-02-01 14:54 ` Boris Ostrovsky
2016-02-01 16:56 ` Jan Beulich [this message]
2016-02-01 19:17 ` Boris Ostrovsky
2016-02-02 9:32 ` Jan Beulich
2016-02-02 15:51 ` Jan Beulich
2016-02-02 16:16 ` PGNet Dev
2016-02-01 10:28 ` Roger Pau Monné
2016-02-01 12:30 ` PGNet Dev
2016-02-01 14:11 ` Boris Ostrovsky
2016-02-01 15:49 ` PGNet Dev
2016-02-01 19:14 ` Boris Ostrovsky
2016-02-01 19:27 ` PGNet Dev
2016-02-01 19:58 ` Boris Ostrovsky
2016-02-01 23:49 ` Brendan Gregg
2016-02-02 15:28 ` Boris Ostrovsky
2016-02-04 22:01 ` PGNet Dev
2016-02-04 22:39 ` Boris Ostrovsky
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=56AF9C3502000078000CD238@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=pgnet.dev@gmail.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.