Re: [Xen-devel] Clarifying PVH mode requirements

[Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>]

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)/EndEntire 
>
> /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@xxxxxxx) (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")
-boris

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