* [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
@ 2019-10-28 10:32 Sander Eikelenboom
2019-10-28 10:38 ` Jan Beulich
2019-10-30 15:48 ` Jan Beulich
0 siblings, 2 replies; 15+ messages in thread
From: Sander Eikelenboom @ 2019-10-28 10:32 UTC (permalink / raw)
To: Jan Beulich, Andrew Cooper; +Cc: xen-devel
Hi Jan / Andrew,
While testing the latest xen-unstable and starting an HVM guest with pci-passtrough on my AMD machine,
my eye catched the following messages in xl dmesg I haven't seen before:
(XEN) [2019-10-28 10:23:16.372] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
(XEN) [2019-10-28 10:24:08.136] AMD-Vi: INVALID_DEV_REQUEST 00000800 8a000000 f8000240 000000fd
Probably something from the AMD iommu rework that got committed lately ?
I you need a complete debug log from host boot or want me to run some debug patches,
please let me know.
--
Sander
(XEN) [2019-10-28 10:23:16.372] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: CPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: CPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: CPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: CPU
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: PIC
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: IOAPIC
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: LAPIC
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: LAPIC
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: LAPIC
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: LAPIC
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: LAPIC_REGS
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: LAPIC_REGS
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: LAPIC_REGS
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: LAPIC_REGS
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: PCI_IRQ
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: ISA_IRQ
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: PCI_LINK
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: PIT
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: RTC
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: HPET
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: PMTIMER
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: MTRR
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: MTRR
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: MTRR
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: MTRR
(XEN) [2019-10-28 10:23:16.605] HVM d18 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: CPU_XSAVE
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: CPU_XSAVE
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: CPU_XSAVE
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: CPU_XSAVE
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: VIRIDIAN_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: VIRIDIAN_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: VMCE_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: VMCE_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: VMCE_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: VMCE_VCPU
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: TSC_ADJUST
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: TSC_ADJUST
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: TSC_ADJUST
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: TSC_ADJUST
(XEN) [2019-10-28 10:23:16.605] HVM d18v0 save: CPU_MSR
(XEN) [2019-10-28 10:23:16.605] HVM d18v1 save: CPU_MSR
(XEN) [2019-10-28 10:23:16.605] HVM d18v2 save: CPU_MSR
(XEN) [2019-10-28 10:23:16.605] HVM d18v3 save: CPU_MSR
(XEN) [2019-10-28 10:23:16.605] HVM18 restore: CPU 0
(XEN) [2019-10-28 10:23:21.950] d18: bind: m_gsi=37 g_gsi=36 dev=00.00.5 intx=0
(XEN) [2019-10-28 10:23:21.976] AMD-Vi: Disable: device id = 0x800, domain = 0, paging mode = 3
(XEN) [2019-10-28 10:23:21.976] AMD-Vi: Setup I/O page table: device id = 0x800, type = 0x1, root table = 0x40f3c1000, domain = 18, paging mode = 3
(XEN) [2019-10-28 10:23:21.976] AMD-Vi: Re-assign 0000:08:00.0 from dom0 to dom18
(d18) [2019-10-28 10:23:22.030] HVM Loader
(d18) [2019-10-28 10:23:22.030] Detected Xen v4.13.0-rc
(d18) [2019-10-28 10:23:22.030] Xenbus rings @0xfeffc000, event channel 1
(d18) [2019-10-28 10:23:22.030] System requested SeaBIOS
(d18) [2019-10-28 10:23:22.030] CPU speed is 3200 MHz
(d18) [2019-10-28 10:23:22.030] Relocating guest memory for lowmem MMIO space disabled
(XEN) [2019-10-28 10:23:22.039] irq.c:374: Dom18 PCI link 0 changed 0 -> 5
(d18) [2019-10-28 10:23:22.039] PCI-ISA link 0 routed to IRQ5
(XEN) [2019-10-28 10:23:22.048] irq.c:374: Dom18 PCI link 1 changed 0 -> 10
(d18) [2019-10-28 10:23:22.048] PCI-ISA link 1 routed to IRQ10
(XEN) [2019-10-28 10:23:22.056] irq.c:374: Dom18 PCI link 2 changed 0 -> 11
(d18) [2019-10-28 10:23:22.056] PCI-ISA link 2 routed to IRQ11
(XEN) [2019-10-28 10:23:22.063] irq.c:374: Dom18 PCI link 3 changed 0 -> 5
(d18) [2019-10-28 10:23:22.063] PCI-ISA link 3 routed to IRQ5
(d18) [2019-10-28 10:23:22.101] pci dev 01:3 INTA->IRQ10
(d18) [2019-10-28 10:23:22.103] pci dev 02:0 INTA->IRQ11
(d18) [2019-10-28 10:23:22.107] pci dev 04:0 INTA->IRQ5
(d18) [2019-10-28 10:23:22.109] pci dev 05:0 INTA->IRQ10
(d18) [2019-10-28 10:23:22.122] RAM in high memory; setting high_mem resource base to 10f800000
(d18) [2019-10-28 10:23:22.122] pci dev 03:0 bar 10 size 002000000: 0f0000008
(d18) [2019-10-28 10:23:22.122] pci dev 02:0 bar 14 size 001000000: 0f2000008
(d18) [2019-10-28 10:23:22.123] pci dev 04:0 bar 30 size 000040000: 0f3000000
(d18) [2019-10-28 10:23:22.124] pci dev 04:0 bar 10 size 000020000: 0f3040000
(d18) [2019-10-28 10:23:22.124] pci dev 03:0 bar 30 size 000010000: 0f3060000
(d18) [2019-10-28 10:23:22.124] pci dev 05:0 bar 10 size 000002000: 0f3070004
(XEN) [2019-10-28 10:23:22.124] memory_map:add: dom18 gfn=f3070 mfn=fe3fe nr=1
(d18) [2019-10-28 10:23:22.127] pci dev 03:0 bar 14 size 000001000: 0f3072000
(d18) [2019-10-28 10:23:22.127] pci dev 02:0 bar 10 size 000000100: 00000c001
(d18) [2019-10-28 10:23:22.128] pci dev 04:0 bar 14 size 000000040: 00000c101
(d18) [2019-10-28 10:23:22.129] pci dev 01:1 bar 20 size 000000010: 00000c141
(d18) [2019-10-28 10:23:22.129] Multiprocessor initialisation:
(d18) [2019-10-28 10:23:22.131] - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d18) [2019-10-28 10:23:22.133] - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d18) [2019-10-28 10:23:22.136] - CPU2 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d18) [2019-10-28 10:23:22.138] - CPU3 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d18) [2019-10-28 10:23:22.138] Testing HVM environment:
(d18) [2019-10-28 10:23:22.138] Using scratch memory at 400000
(d18) [2019-10-28 10:23:22.150] - REP INSB across page boundaries ... passed
(d18) [2019-10-28 10:23:22.163] - REP INSW across page boundaries ... passed
(d18) [2019-10-28 10:23:22.174] - GS base MSRs and SWAPGS ... passed
(d18) [2019-10-28 10:23:22.174] Passed 3 of 3 tests
(d18) [2019-10-28 10:23:22.174] Writing SMBIOS tables ...
(d18) [2019-10-28 10:23:22.176] Loading SeaBIOS ...
(d18) [2019-10-28 10:23:22.176] Creating MP tables ...
(d18) [2019-10-28 10:23:22.176] Loading ACPI ...
(d18) [2019-10-28 10:23:22.177] vm86 TSS at fc00aa00
(d18) [2019-10-28 10:23:22.177] BIOS map:
(d18) [2019-10-28 10:23:22.177] 10000-100e3: Scratch space
(d18) [2019-10-28 10:23:22.177] c0000-fffff: Main BIOS
(d18) [2019-10-28 10:23:22.177] E820 table:
(d18) [2019-10-28 10:23:22.177] [00]: 00000000:00000000 - 00000000:000a0000: RAM
(d18) [2019-10-28 10:23:22.177] HOLE: 00000000:000a0000 - 00000000:000c0000
(d18) [2019-10-28 10:23:22.177] [01]: 00000000:000c0000 - 00000000:00100000: RESERVED
(d18) [2019-10-28 10:23:22.178] [02]: 00000000:00100000 - 00000000:f0000000: RAM
(d18) [2019-10-28 10:23:22.178] HOLE: 00000000:f0000000 - 00000000:fc000000
(d18) [2019-10-28 10:23:22.178] [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d18) [2019-10-28 10:23:22.178] [04]: 00000001:00000000 - 00000001:0f800000: RAM
(d18) [2019-10-28 10:23:22.178] Invoking SeaBIOS ...
(d18) [2019-10-28 10:23:22.178] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d18) [2019-10-28 10:23:22.178] BUILD: gcc: (Debian 8.3.0-6) 8.3.0 binutils: (GNU Binutils for Debian) 2.31.1
(d18) [2019-10-28 10:23:22.178]
(d18) [2019-10-28 10:23:22.178] Found Xen hypervisor signature at 40000000
(d18) [2019-10-28 10:23:22.178] Running on QEMU (i440fx)
(d18) [2019-10-28 10:23:22.178] xen: copy e820...
(d18) [2019-10-28 10:23:22.178] Relocating init from 0x000d8920 to 0xeffac480 (size 80608)
(d18) [2019-10-28 10:23:22.179] Found QEMU fw_cfg
(d18) [2019-10-28 10:23:22.180] RamSizeOver4G: 0x000000000f800000 [cmos]
(d18) [2019-10-28 10:23:22.180] boot order:
(d18) [2019-10-28 10:23:22.180] 1: /rom@genroms/linuxboot.bin
(d18) [2019-10-28 10:23:22.182] Found 8 PCI devices (max PCI bus is 00)
(d18) [2019-10-28 10:23:22.183] Allocated Xen hypercall page at effff000
(d18) [2019-10-28 10:23:22.183] Detected Xen v4.13.0-rc
(d18) [2019-10-28 10:23:22.183] xen: copy BIOS tables...
(d18) [2019-10-28 10:23:22.183] Copying SMBIOS entry point from 0x00010020 to 0x000f5be0
(d18) [2019-10-28 10:23:22.183] Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5ac0
(d18) [2019-10-28 10:23:22.183] Copying PIR from 0x00010040 to 0x000f5a40
(d18) [2019-10-28 10:23:22.183] Copying ACPI RSDP from 0x000100c0 to 0x000f5a10
(d18) [2019-10-28 10:23:22.183] Using pmtimer, ioport 0xb008
(d18) [2019-10-28 10:23:22.183] Scan for VGA option rom
(d18) [2019-10-28 10:23:22.193] Running option rom at c000:0003
(XEN) [2019-10-28 10:23:22.193] stdvga.c:173:d18v0 entering stdvga mode
(d18) [2019-10-28 10:23:22.202] pmm call arg1=0
(d18) [2019-10-28 10:23:22.202] Turning on vga text mode console
(d18) [2019-10-28 10:23:22.244] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d18) [2019-10-28 10:23:22.248] Machine UUID 74135651-a6eb-4e9f-966b-b364f0a5bee3
(d18) [2019-10-28 10:23:22.249] XHCI init on dev 00:05.0: regs @ 0xf3070000, 4 ports, 32 slots, 32 byte contexts
(d18) [2019-10-28 10:23:22.249] XHCI extcap 0x1 @ 0xf3070500
(d18) [2019-10-28 10:23:22.249] XHCI protocol USB 3.00, 2 ports (offset 1), def 0
(d18) [2019-10-28 10:23:22.249] XHCI protocol USB 2.00, 2 ports (offset 3), def 0
(d18) [2019-10-28 10:23:22.249] ATA controller 1 at 1f0/3f4/c140 (irq 14 dev 9)
(d18) [2019-10-28 10:23:22.250] ATA controller 2 at 170/374/c148 (irq 15 dev 9)
(d18) [2019-10-28 10:23:22.251] Found 0 lpt ports
(d18) [2019-10-28 10:23:22.251] Found 1 serial ports
(d18) [2019-10-28 10:23:22.252] PS2 keyboard initialized
(d18) [2019-10-28 10:23:22.252] ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (10240 MiBytes)
(d18) [2019-10-28 10:23:22.252] Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(d18) [2019-10-28 10:23:22.253] ata0-1: QEMU HARDDISK ATA-7 Hard-Disk (800 GiBytes)
(d18) [2019-10-28 10:23:22.253] Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(d18) [2019-10-28 10:23:22.254] ata1-0: QEMU HARDDISK ATA-7 Hard-Disk (250 GiBytes)
(d18) [2019-10-28 10:23:22.254] Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(d18) [2019-10-28 10:23:22.255] ata1-1: QEMU HARDDISK ATA-7 Hard-Disk (260 GiBytes)
(d18) [2019-10-28 10:23:22.255] Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@1
(d18) [2019-10-28 10:23:22.375] XHCI port #4: 0x00200a03, powered, enabled, pls 0, speed 2 [Low]
(d18) [2019-10-28 10:23:22.414] XHCI no devices found
(d18) [2019-10-28 10:23:22.421] All threads complete.
(d18) [2019-10-28 10:23:22.421] Scan for option roms
(d18) [2019-10-28 10:23:22.442] Running option rom at c980:0003
(d18) [2019-10-28 10:23:22.448] pmm call arg1=1
(d18) [2019-10-28 10:23:22.448] pmm call arg1=0
(d18) [2019-10-28 10:23:22.449] pmm call arg1=1
(d18) [2019-10-28 10:23:22.449] pmm call arg1=0
(d18) [2019-10-28 10:23:22.465] Running option rom at ca80:0003
(d18) [2019-10-28 10:23:22.465] Searching bootorder for: /pci@i0cf8/*@4
(d18) [2019-10-28 10:23:22.466] Searching bootorder for: /rom@genroms/linuxboot.bin
(d18) [2019-10-28 10:23:22.466] Searching bootorder for: HALT
(d18) [2019-10-28 10:23:22.466] drive 0x000f59a0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=20971520
(d18) [2019-10-28 10:23:22.466] drive 0x000f5970: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=1677721600
(d18) [2019-10-28 10:23:22.466] drive 0x000f5940: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=524288000
(d18) [2019-10-28 10:23:22.466] drive 0x000f5910: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=545259520
(d18) [2019-10-28 10:23:22.466] Space available for UMB: cb000-eb800, f5400-f5910
(d18) [2019-10-28 10:23:22.466] Returned 253952 bytes of ZoneHigh
(d18) [2019-10-28 10:23:22.466] e820 map has 7 items:
(d18) [2019-10-28 10:23:22.466] 0: 0000000000000000 - 000000000009fc00 = 1 RAM
(d18) [2019-10-28 10:23:22.466] 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(d18) [2019-10-28 10:23:22.466] 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(d18) [2019-10-28 10:23:22.467] 3: 0000000000100000 - 00000000efffe000 = 1 RAM
(d18) [2019-10-28 10:23:22.467] 4: 00000000efffe000 - 00000000f0000000 = 2 RESERVED
(d18) [2019-10-28 10:23:22.467] 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(d18) [2019-10-28 10:23:22.467] 6: 0000000100000000 - 000000010f800000 = 1 RAM
(d18) [2019-10-28 10:23:22.468] enter handle_19:
(d18) [2019-10-28 10:23:22.468] NULL
(d18) [2019-10-28 10:23:22.471] Booting from ROM...
(d18) [2019-10-28 10:23:22.471] Booting from ca80:003c
(XEN) [2019-10-28 10:24:03.428] Dom18 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-28 10:24:06.103] memory_map:remove: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.106] memory_map:add: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.117] memory_map:remove: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.120] memory_map:add: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.123] memory_map:remove: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.125] memory_map:add: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.128] memory_map:remove: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.130] memory_map:add: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.132] memory_map:remove: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.135] memory_map:add: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.137] memory_map:remove: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.140] memory_map:add: dom18 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-28 10:24:06.155] irq.c:374: Dom18 PCI link 0 changed 5 -> 0
(XEN) [2019-10-28 10:24:06.162] irq.c:374: Dom18 PCI link 1 changed 10 -> 0
(XEN) [2019-10-28 10:24:06.170] irq.c:374: Dom18 PCI link 2 changed 11 -> 0
(XEN) [2019-10-28 10:24:06.177] irq.c:374: Dom18 PCI link 3 changed 5 -> 0
(XEN) [2019-10-28 10:24:08.045] grant_table.c:1786:d18v2 Expanding d18 grant table from 1 to 2 frames
(XEN) [2019-10-28 10:24:08.045] grant_table.c:1786:d18v2 Expanding d18 grant table from 2 to 3 frames
(XEN) [2019-10-28 10:24:08.045] grant_table.c:1786:d18v2 Expanding d18 grant table from 3 to 4 frames
(XEN) [2019-10-28 10:24:08.045] grant_table.c:1786:d18v2 Expanding d18 grant table from 4 to 5 frames
(XEN) [2019-10-28 10:24:08.136] AMD-Vi: INVALID_DEV_REQUEST 00000800 8a000000 f8000240 000000fd
(XEN) [2019-10-28 10:24:15.963] grant_table.c:1786:d18v1 Expanding d18 grant table from 5 to 6 frames
(XEN) [2019-10-28 10:24:26.342] grant_table.c:1786:d18v1 Expanding d18 grant table from 6 to 7 frames
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-28 10:32 [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock Sander Eikelenboom
@ 2019-10-28 10:38 ` Jan Beulich
2019-10-30 15:48 ` Jan Beulich
1 sibling, 0 replies; 15+ messages in thread
From: Jan Beulich @ 2019-10-28 10:38 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, xen-devel
On 28.10.2019 11:32, Sander Eikelenboom wrote:
> Hi Jan / Andrew,
>
> While testing the latest xen-unstable and starting an HVM guest with pci-passtrough on my AMD machine,
> my eye catched the following messages in xl dmesg I haven't seen before:
>
> (XEN) [2019-10-28 10:23:16.372] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
> (XEN) [2019-10-28 10:24:08.136] AMD-Vi: INVALID_DEV_REQUEST 00000800 8a000000 f8000240 000000fd
>
> Probably something from the AMD iommu rework that got committed lately ?
Not very likely at least for the former; I'll have to look at the
latter in some more detail (and at both to see whether I can spot
a sensible solution).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-28 10:32 [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock Sander Eikelenboom
2019-10-28 10:38 ` Jan Beulich
@ 2019-10-30 15:48 ` Jan Beulich
2019-10-30 22:21 ` Sander Eikelenboom
1 sibling, 1 reply; 15+ messages in thread
From: Jan Beulich @ 2019-10-30 15:48 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, xen-devel
On 28.10.2019 11:32, Sander Eikelenboom wrote:
> While testing the latest xen-unstable and starting an HVM guest with pci-passtrough on my AMD machine,
> my eye catched the following messages in xl dmesg I haven't seen before:
>
> (XEN) [2019-10-28 10:23:16.372] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
Unfortunately this sits on the map/unmap path, and hence the
violator is far up one of the many call chains. Therefore I'd
like to ask that you rebuild and retry with the debugging
patch below. In case you observe multiple different call
trees, post them all please.
Jan
--- unstable.orig/xen/drivers/passthrough/amd/iommu_map.c
+++ unstable/xen/drivers/passthrough/amd/iommu_map.c
@@ -331,9 +331,12 @@ static int update_paging_mode(struct dom
hd->arch.paging_mode = level;
hd->arch.root_table = new_root;
- if ( !pcidevs_locked() )
+ if ( iommu_debug && !pcidevs_locked() )
+ {
AMD_IOMMU_DEBUG("%s Try to access pdev_list "
"without aquiring pcidevs_lock.\n", __func__);
+ dump_execution_state();
+ }
/* Update device table entries using new root table and paging mode */
for_each_pdev( d, pdev )
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-30 15:48 ` Jan Beulich
@ 2019-10-30 22:21 ` Sander Eikelenboom
2019-10-31 7:31 ` Jan Beulich
2019-10-31 10:15 ` Jan Beulich
0 siblings, 2 replies; 15+ messages in thread
From: Sander Eikelenboom @ 2019-10-30 22:21 UTC (permalink / raw)
To: Jan Beulich; +Cc: Andrew Cooper, xen-devel
On 30/10/2019 16:48, Jan Beulich wrote:
> On 28.10.2019 11:32, Sander Eikelenboom wrote:
>> While testing the latest xen-unstable and starting an HVM guest with pci-passtrough on my AMD machine,
>> my eye catched the following messages in xl dmesg I haven't seen before:
>>
>> (XEN) [2019-10-28 10:23:16.372] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
>
> Unfortunately this sits on the map/unmap path, and hence the
> violator is far up one of the many call chains. Therefore I'd
> like to ask that you rebuild and retry with the debugging
> patch below. In case you observe multiple different call
> trees, post them all please.
>
> Jan
Hi Jan,
Call trace seems to be the same in all cases.
--
Sander
(XEN) [2019-10-30 22:07:05.748] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
(XEN) [2019-10-30 22:07:05.748] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
(XEN) [2019-10-30 22:07:05.748] CPU: 1
(XEN) [2019-10-30 22:07:05.748] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:05.748] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v2)
(XEN) [2019-10-30 22:07:05.748] rax: ffff830523f9ffff rbx: ffff82e004905f00 rcx: 0000000000000000
(XEN) [2019-10-30 22:07:05.748] rdx: 0000000000000001 rsi: 000000000000000a rdi: ffff82d0804a0698
(XEN) [2019-10-30 22:07:05.748] rbp: ffff830523f9f848 rsp: ffff830523f9f808 r8: ffff8305320a0000
(XEN) [2019-10-30 22:07:05.748] r9: 0000000000000038 r10: 0000000000000002 r11: 000000000000000a
(XEN) [2019-10-30 22:07:05.748] r12: ffff82e004905f00 r13: 0000000000000003 r14: 0000000000000003
(XEN) [2019-10-30 22:07:05.748] r15: ffff83041fb83000 cr0: 0000000080050033 cr4: 00000000000006e0
(XEN) [2019-10-30 22:07:05.748] cr3: 000000040a58d000 cr2: ffff8880604835a0
(XEN) [2019-10-30 22:07:05.748] fsb: 00007f4b8f899bc0 gsb: ffff88807d480000 gss: 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) [2019-10-30 22:07:05.748] Xen code around <ffff82d080265748> (iommu_map.c#update_paging_mode+0x1f2/0x3eb):
(XEN) [2019-10-30 22:07:05.748] 3d 3b 7b 22 00 00 75 07 <0f> 0b e9 c2 01 00 00 48 8d 35 1a ce 13 00 48 8d
(XEN) [2019-10-30 22:07:05.748] Xen stack trace from rsp=ffff830523f9f808:
(XEN) [2019-10-30 22:07:05.748] ffff82e00a6bc6e0 ffff82e00a6bc6e0 ffff83041fb83000 ffff83041fb83000
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83148 00000000000feff8 ffff83041fb83150 ffff830523f9f93c
(XEN) [2019-10-30 22:07:05.748] ffff830523f9f8c8 ffff82d080265ded 0000000380240580 00000000002482f9
(XEN) [2019-10-30 22:07:05.748] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83000 00000000000feff8 00000000000feff8 00000000002482f9
(XEN) [2019-10-30 22:07:05.748] ffff830523f9f928 ffff82d0802583b6 00000000000feff8 0000000000000001
(XEN) [2019-10-30 22:07:05.748] 00000003802405da 00000000002482f9 ffff830523f9f93c 0000000000000003
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83000 00000000000feff8 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ffff830523f9f960 ffff82d0802586fb 0000000048834780 0000000000000003
(XEN) [2019-10-30 22:07:05.748] 0000000000000000 ffff830248834780 00000000000feff8 ffff830523f9f9f8
(XEN) [2019-10-30 22:07:05.748] ffff82d08034a4a6 000000008038a845 0000000000000000 ffff820040024fc0
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83000 00000000002482f9 0000000000000000 80000002484b5367
(XEN) [2019-10-30 22:07:05.748] ffff82004002d5a0 80000002484b5367 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ffff820040024000 0000000000000000 00000000002482f9 00000000000feff8
(XEN) [2019-10-30 22:07:05.748] 0000000000000001 ffff830248834780 ffff830523f9fa50 ffff82d080342e13
(XEN) [2019-10-30 22:07:05.748] ffffffffffffffff 0000000000000007 ffff83041fb83000 0000000000000023
(XEN) [2019-10-30 22:07:05.748] 00000000002482fa ffff830248834780 0000000000000000 00000000002482f9
(XEN) [2019-10-30 22:07:05.748] 00000000000feff8 ffff830523f9fac8 ffff82d080343c52 0000000023f9fa78
(XEN) [2019-10-30 22:07:05.748] 0000000000000001 00000000002482f9 00000000000feff8 ffff830523f9fa98
(XEN) [2019-10-30 22:07:05.748] Xen call trace:
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
(XEN) [2019-10-30 22:07:05.748] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802221e8>] F do_memory_op+0x695/0x1bf7
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080383601>] F pv_hypercall+0x2ca/0x537
(XEN) [2019-10-30 22:07:05.748] [<ffff82d08038a432>] F lstar_enter+0x112/0x120
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-30 22:21 ` Sander Eikelenboom
@ 2019-10-31 7:31 ` Jan Beulich
2019-10-31 8:35 ` Sander Eikelenboom
2019-10-31 10:15 ` Jan Beulich
1 sibling, 1 reply; 15+ messages in thread
From: Jan Beulich @ 2019-10-31 7:31 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, xen-devel
On 30.10.2019 23:21, Sander Eikelenboom wrote:
> Call trace seems to be the same in all cases.
Thanks much.
> (XEN) [2019-10-30 22:07:05.748] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
> (XEN) [2019-10-30 22:07:05.748] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
> (XEN) [2019-10-30 22:07:05.748] CPU: 1
> (XEN) [2019-10-30 22:07:05.748] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
> (XEN) [2019-10-30 22:07:05.748] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v2)
> (XEN) [2019-10-30 22:07:05.748] rax: ffff830523f9ffff rbx: ffff82e004905f00 rcx: 0000000000000000
> (XEN) [2019-10-30 22:07:05.748] rdx: 0000000000000001 rsi: 000000000000000a rdi: ffff82d0804a0698
> (XEN) [2019-10-30 22:07:05.748] rbp: ffff830523f9f848 rsp: ffff830523f9f808 r8: ffff8305320a0000
> (XEN) [2019-10-30 22:07:05.748] r9: 0000000000000038 r10: 0000000000000002 r11: 000000000000000a
> (XEN) [2019-10-30 22:07:05.748] r12: ffff82e004905f00 r13: 0000000000000003 r14: 0000000000000003
> (XEN) [2019-10-30 22:07:05.748] r15: ffff83041fb83000 cr0: 0000000080050033 cr4: 00000000000006e0
> (XEN) [2019-10-30 22:07:05.748] cr3: 000000040a58d000 cr2: ffff8880604835a0
> (XEN) [2019-10-30 22:07:05.748] fsb: 00007f4b8f899bc0 gsb: ffff88807d480000 gss: 0000000000000000
> (XEN) [2019-10-30 22:07:05.748] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
> (XEN) [2019-10-30 22:07:05.748] Xen code around <ffff82d080265748> (iommu_map.c#update_paging_mode+0x1f2/0x3eb):
> (XEN) [2019-10-30 22:07:05.748] 3d 3b 7b 22 00 00 75 07 <0f> 0b e9 c2 01 00 00 48 8d 35 1a ce 13 00 48 8d
> (XEN) [2019-10-30 22:07:05.748] Xen stack trace from rsp=ffff830523f9f808:
[...]
> (XEN) [2019-10-30 22:07:05.748] Xen call trace:
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802221e8>] F do_memory_op+0x695/0x1bf7
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080383601>] F pv_hypercall+0x2ca/0x537
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d08038a432>] F lstar_enter+0x112/0x120
Now this looks to be a pretty common path, i.e. I wonder why no-one
before has noticed this message getting logged. Fixing, as it seems,
will require careful auditing of lock nesting, as the PCI devices
lock will need to be acquired on a path that's entirely unrelated to
any PCI operation; I'll try to get to this asap. Is there anything
special about the guest that triggers this?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-31 7:31 ` Jan Beulich
@ 2019-10-31 8:35 ` Sander Eikelenboom
2019-10-31 9:18 ` Jan Beulich
0 siblings, 1 reply; 15+ messages in thread
From: Sander Eikelenboom @ 2019-10-31 8:35 UTC (permalink / raw)
To: Jan Beulich; +Cc: Andrew Cooper, xen-devel
[-- Attachment #1: Type: text/plain, Size: 4591 bytes --]
On 31/10/2019 08:31, Jan Beulich wrote:
> On 30.10.2019 23:21, Sander Eikelenboom wrote:
>> Call trace seems to be the same in all cases.
>
> Thanks much.
>
>> (XEN) [2019-10-30 22:07:05.748] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
>> (XEN) [2019-10-30 22:07:05.748] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
>> (XEN) [2019-10-30 22:07:05.748] CPU: 1
>> (XEN) [2019-10-30 22:07:05.748] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
>> (XEN) [2019-10-30 22:07:05.748] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v2)
>> (XEN) [2019-10-30 22:07:05.748] rax: ffff830523f9ffff rbx: ffff82e004905f00 rcx: 0000000000000000
>> (XEN) [2019-10-30 22:07:05.748] rdx: 0000000000000001 rsi: 000000000000000a rdi: ffff82d0804a0698
>> (XEN) [2019-10-30 22:07:05.748] rbp: ffff830523f9f848 rsp: ffff830523f9f808 r8: ffff8305320a0000
>> (XEN) [2019-10-30 22:07:05.748] r9: 0000000000000038 r10: 0000000000000002 r11: 000000000000000a
>> (XEN) [2019-10-30 22:07:05.748] r12: ffff82e004905f00 r13: 0000000000000003 r14: 0000000000000003
>> (XEN) [2019-10-30 22:07:05.748] r15: ffff83041fb83000 cr0: 0000000080050033 cr4: 00000000000006e0
>> (XEN) [2019-10-30 22:07:05.748] cr3: 000000040a58d000 cr2: ffff8880604835a0
>> (XEN) [2019-10-30 22:07:05.748] fsb: 00007f4b8f899bc0 gsb: ffff88807d480000 gss: 0000000000000000
>> (XEN) [2019-10-30 22:07:05.748] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
>> (XEN) [2019-10-30 22:07:05.748] Xen code around <ffff82d080265748> (iommu_map.c#update_paging_mode+0x1f2/0x3eb):
>> (XEN) [2019-10-30 22:07:05.748] 3d 3b 7b 22 00 00 75 07 <0f> 0b e9 c2 01 00 00 48 8d 35 1a ce 13 00 48 8d
>> (XEN) [2019-10-30 22:07:05.748] Xen stack trace from rsp=ffff830523f9f808:
> [...]
>> (XEN) [2019-10-30 22:07:05.748] Xen call trace:
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802221e8>] F do_memory_op+0x695/0x1bf7
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080383601>] F pv_hypercall+0x2ca/0x537
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d08038a432>] F lstar_enter+0x112/0x120
>
> Now this looks to be a pretty common path, i.e. I wonder why no-one
> before has noticed this message getting logged. Fixing, as it seems,
> will require careful auditing of lock nesting, as the PCI devices
> lock will need to be acquired on a path that's entirely unrelated to
> any PCI operation; I'll try to get to this asap. Is there anything
> special about the guest that triggers this?
Not that I am aware of.
I run with amd iommu debug on, others perhaps don't so you don't get the message ?
Platform is perhaps what specific (older AMD 890FX chipset) and I need the bios workaround:
ivrs_ioapic[6]=00:14.0 iommu=on.
On the other hand, this has ran like this for quite some time.
I have 3 guests (HVM) for which i use PCI passthrough and
for each of those 3 guests I get this message *once* on start of the guest.
One guest has a soundcard passed through,
One guest has a USB2 card passed through,
One guest has a USB3 card passed through.
Another observation is that both the soundcard and USB2 card
still seem to function despite the message.
The USB3 controller goes haywire though (a lot of driver messages in the guest during init).
I could try to bisect, but that would be somewhere next week before I can get to that.
At present I run with a tree with as latest commit ee7170822f1fc209f33feb47b268bab35541351d,
which is stable for me. This predates some of the IOMMU changes and Anthony's QMP work that had
some issues, but that would be the last known real good point for me to start a bisect from.
I have attached the complete xl dmesg output.
--
Sander
> Jan
>
[-- Attachment #2: xl-dmesg.txt --]
[-- Type: text/plain, Size: 111901 bytes --]
__ __ _ _ _ _____ ___
\ \/ /___ _ __ | || | / |___ / / _ \ _ __ ___
\ // _ \ '_ \ | || |_ | | |_ \| | | |__| '__/ __|
/ \ __/ | | | |__ _|| |___) | |_| |__| | | (__
/_/\_\___|_| |_| |_|(_)_|____(_)___/ |_| \___|
(XEN) [0000001a2bd698a3] Xen version 4.13.0-rc (root@dyndns.org) (gcc (Debian 8.3.0-6) 8.3.0) debug=y Wed Oct 30 22:56:09 CET 2019
(XEN) [0000001a326f0c9a] Latest ChangeSet: Tue Oct 29 16:39:59 2019 +0000 git:bd4fdc49fa-dirty
(XEN) [0000001a3731d14a] build-id: 2ba93da01fac20cd8b42eef229e3d403f9d0a485
(XEN) [0000001a3b035030] Bootloader: GRUB 2.02+dfsg1-20
(XEN) [0000001a3dd6fe98] Command line: dom0_mem=2048M,max:2048M loglvl=all guest_loglvl=all console_timestamps=datems vga=gfx-1280x1024x32 no-cpuidle com1=38400,8n1 console=vga,com1 ivrs_ioapic[6]=00:14.0 iommu=on,verbose,debug conring_size=128k ucode=scan sched=credit2 gnttab_max_frames=64 reboot=k
(XEN) [0000001a4cd0f7f2] Xen image load base address: 0
(XEN) [0000001a4fa4a263] Video information:
(XEN) [0000001a51dfe3c6] VGA is graphics mode 1280x1024, 32 bpp
(XEN) [0000001a5525c603] VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) [0000001a59040f50] EDID info not retrieved because of reasons unknown
(XEN) [0000001a5ce23f43] Disc information:
(XEN) [0000001a5f10cd00] Found 4 MBR signatures
(XEN) [0000001a618ba126] Found 4 EDD information structures
(XEN) [0000001a649eb5aa] Xen-e820 RAM map:
(XEN) [0000001a66cd4793] 0000000000000000 - 0000000000096400 (usable)
(XEN) [0000001a6a5f7133] 0000000000096400 - 00000000000a0000 (reserved)
(XEN) [0000001a6e0ad828] 00000000000e4000 - 0000000000100000 (reserved)
(XEN) [0000001a71b643a2] 0000000000100000 - 00000000c7f90000 (usable)
(XEN) [0000001a75486da2] 00000000c7f90000 - 00000000c7f9e000 (ACPI data)
(XEN) [0000001a7900892e] 00000000c7f9e000 - 00000000c7fe0000 (ACPI NVS)
(XEN) [0000001a7cabf773] 00000000c7fe0000 - 00000000c8000000 (reserved)
(XEN) [0000001a805761fb] 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) [0000001a8402e9c2] 0000000100000000 - 0000000538000000 (usable)
(XEN) [0000001a8f5b94c8] New Xen image base address: 0xc7800000
(XEN) [0000001a9294b692] ACPI: RSDP 000FB100, 0014 (r0 ACPIAM)
(XEN) [0000001a95c1467a] ACPI: RSDT C7F90000, 0048 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) [0000001a9a83fabe] ACPI: FACP C7F90200, 0084 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) [0000001a9f46d292] ACPI: DSDT C7F905E0, 9427 (r1 A7640 A7640100 100 INTL 20051117)
(XEN) [0000001aa40977be] ACPI: FACS C7F9E000, 0040
(XEN) [0000001aa69dba58] ACPI: APIC C7F90390, 0088 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) [0000001aab6061cb] ACPI: MCFG C7F90420, 003C (r1 7640MS OEMMCFG 20100913 MSFT 97)
(XEN) [0000001ab023252b] ACPI: SLIC C7F90460, 0176 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) [0000001ab4e5eb8b] ACPI: OEMB C7F9E040, 0072 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) [0000001ab9a8b8ab] ACPI: SRAT C7F9A5E0, 0108 (r3 AMD FAM_F_10 2 AMD 1)
(XEN) [0000001abe6b5c8b] ACPI: HPET C7F9A6F0, 0038 (r1 7640MS OEMHPET 20100913 MSFT 97)
(XEN) [0000001ac32e26de] ACPI: IVRS C7F9A730, 0108 (r1 AMD RD890S 202031 AMD 0)
(XEN) [0000001ac7f0ebb8] ACPI: SSDT C7F9A840, 0DA4 (r1 A M I POWERNOW 1 AMD 1)
(XEN) [0000001accb3a7c8] System RAM: 20479MB (20970648kB)
(XEN) [0000001ad6ecc362] SRAT: PXM 0 -> APIC 00 -> Node 0
(XEN) [0000001ad9d9d90a] SRAT: PXM 0 -> APIC 01 -> Node 0
(XEN) [0000001adcc6e686] SRAT: PXM 0 -> APIC 02 -> Node 0
(XEN) [0000001adfb3efd6] SRAT: PXM 0 -> APIC 03 -> Node 0
(XEN) [0000001ae2a0f6f0] SRAT: PXM 0 -> APIC 04 -> Node 0
(XEN) [0000001ae58de2d0] SRAT: PXM 0 -> APIC 05 -> Node 0
(XEN) [0000001ae87aff16] SRAT: Node 0 PXM 0 0-a0000
(XEN) [0000001aeb1bc91a] SRAT: Node 0 PXM 0 100000-c8000000
(XEN) [0000001aee223d22] SRAT: Node 0 PXM 0 100000000-538000000
(XEN) [0000001af15b65b6] NUMA: Allocated memnodemap from 5320d4000 - 5320da000
(XEN) [0000001af5530db3] NUMA: Using 8 for the hash shift.
(XEN) [0000001b3e0ae14b] Domain heap initialised
(XEN) [0000001b40859213] Allocated console ring of 128 KiB.
(XEN) [0000001b56aa04d6] vesafb: framebuffer at 0x00000000d0000000, mapped to 0xffff82c000201000, using 6144k, total 16384k
(XEN) [0000001b5cdcec12] vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) [0000001b60faad56] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
(XEN) [0000001b64a696fa] CPU Vendor: AMD, Family 16 (0x10), Model 10 (0xa), Stepping 0 (raw 00100fa0)
(XEN) [0000001b6eb403cd] found SMP MP-table at 000ff780
(XEN) [0000001b71879052] DMI present.
(XEN) [0000001b7376993b] Using APIC driver default
(XEN) [0000001b760ac8f0] ACPI: PM-Timer IO Port: 0x808 (24 bits)
(XEN) [0000001b7950bd02] ACPI: SLEEP INFO: pm1x_cnt[1:804,1:0], pm1x_evt[1:800,1:0]
(XEN) [0000001b7d87d20a] ACPI: wakeup_vec[c7f9e00c], vec_size[20]
(XEN) [0000001b8172ac8a] ACPI: Local APIC address 0xfee00000
(XEN) [0000001b8485cf52] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) [0000001b88576612] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) [0000001b8c28f01a] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) [0000001b8ffa736b] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) [0000001b93cc0333] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) [0000001b979d7e30] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) [0000001b9b6f00de] ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) [0000001b9f800273] IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) [0000001ba3e9f672] ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) [0000001ba8079cda] IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
(XEN) [0000001bac7e4556] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) [0000001bb09c063a] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) [0000001bb4d30d02] ACPI: IRQ0 used by override.
(XEN) [0000001bb78d539a] ACPI: IRQ2 used by override.
(XEN) [0000001bba4783a2] ACPI: IRQ9 used by override.
(XEN) [0000001bbd01bace] Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) [0000001bc093cbb2] ACPI: HPET id: 0x8300 base: 0xfed00000
(XEN) [0000001bc3ccfeae] PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) [0000001bc8766d42] PCI: Not using MCFG for segment 0000 bus 00-ff
(XEN) [0000001bcc1531f6] AMD-Vi: Found MSI capability block at 0x54
(XEN) [0000001bcf811d5b] Using ACPI (MADT) for SMP configuration information
(XEN) [0000001bd35f62c2] SMP: Allowing 6 CPUs (0 hotplug CPUs)
(XEN) [0000001bd68be523] IRQ limits: 56 GSI, 1112 MSI/MSI-X
(XEN) [0000001bd992498a] microcode: CPU0 updated from revision 0x10000bf to 0x10000dc
(XEN) [0000001bdde2c00d] CPU0: AMD Fam10h machine check reporting enabled
(XEN) [0000001be19aee35] Speculative mitigation facilities:
(XEN) [0000001be4a14e7b] Hardware features:
(XEN) [0000001be6f61235] Compiled-in support: INDIRECT_THUNK SHADOW_PAGING
(XEN) [0000001bead4411a] Xen settings: BTI-Thunk LFENCE, SPEC_CTRL: No, Other: BRANCH_HARDEN
(XEN) [0000001bef970ebe] Support for HVM VMs: RSB
(XEN) [0000001bf237ea75] Support for PV VMs: RSB
(XEN) [0000001bf4cc151a] XPTI (64-bit PV only): Dom0 disabled, DomU disabled (without PCID)
(XEN) [0000001bf98209fd] PV L1TF shadowing: Dom0 disabled, DomU disabled
(XEN) [0000001bfd46efab] Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) [0000001c0131ee0a] Initializing Credit2 scheduler
(XEN) [0000001c04058560] load_precision_shift: 18
(XEN) [0000001c0699a67b] load_window_shift: 30
(XEN) [0000001c0907aa35] underload_balance_tolerance: 0
(XEN) [0000001c0be7ffa5] overload_balance_tolerance: -3
(XEN) [0000001c0ec858f2] runqueues arrangement: socket
(XEN) [0000001c119bfd7b] cap enforcement granularity: 10ms
(XEN) [0000001c14a26dd3] load tracking window length 1073741824 ns
(XEN) [0000001c21794a42] Platform timer is 14.318MHz HPET
(XEN) [ 2.952559] Detected 3200.132 MHz processor.
(XEN) [ 2.969171] alt table ffff82d08047a1b0 -> ffff82d0804882f2
(XEN) [ 2.995470] AMD-Vi: IVRS Block: Found type 0x10 flags 0x3e len 0xd8 id 0x2
(XEN) [ 3.017568] AMD-Vi: Using IVHD type 0x10
(XEN) [ 3.030829] AMD-Vi: ACPI Table:
(XEN) [ 3.041749] AMD-Vi: Signature IVRS
(XEN) [ 3.053709] AMD-Vi: Length 0x108
(XEN) [ 3.065146] AMD-Vi: Revision 0x1
(XEN) [ 3.076587] AMD-Vi: CheckSum 0x65
(XEN) [ 3.088287] AMD-Vi: OEM_Id AMD
(XEN) [ 3.099725] AMD-Vi: OEM_Table_Id RD890S
(XEN) [ 3.112986] AMD-Vi: OEM_Revision 0x202031
(XEN) [ 3.126766] AMD-Vi: Creator_Id AMD
(XEN) [ 3.144300] AMD-Vi: Creator_Revision 0
(XEN) [ 3.162551] AMD-Vi: IVRS Block: type 0x10 flags 0x3e len 0xd8 id 0x2
(XEN) [ 3.188421] AMD-Vi: IVHD Device Entry: type 0x3 id 0 flags 0
(XEN) [ 3.212235] AMD-Vi: Dev_Id Range: 0 -> 0x2
(XEN) [ 3.231617] AMD-Vi: IVHD Device Entry: type 0x2 id 0x10 flags 0
(XEN) [ 3.256199] AMD-Vi: IVHD Device Entry: type 0x3 id 0xe00 flags 0
(XEN) [ 3.281029] AMD-Vi: Dev_Id Range: 0xe00 -> 0xe01
(XEN) [ 3.301931] AMD-Vi: IVHD Device Entry: type 0x2 id 0x18 flags 0
(XEN) [ 3.326488] AMD-Vi: IVHD Device Entry: type 0x2 id 0xd00 flags 0
(XEN) [ 3.351304] AMD-Vi: IVHD Device Entry: type 0x2 id 0x28 flags 0
(XEN) [ 3.375859] AMD-Vi: IVHD Device Entry: type 0x2 id 0xc00 flags 0
(XEN) [ 3.400701] AMD-Vi: IVHD Device Entry: type 0x2 id 0x30 flags 0
(XEN) [ 3.425245] AMD-Vi: IVHD Device Entry: type 0x2 id 0xb00 flags 0
(XEN) [ 3.450049] AMD-Vi: IVHD Device Entry: type 0x2 id 0x48 flags 0
(XEN) [ 3.474577] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa00 flags 0
(XEN) [ 3.499343] AMD-Vi: IVHD Device Entry: type 0x2 id 0x50 flags 0
(XEN) [ 3.523832] AMD-Vi: IVHD Device Entry: type 0x3 id 0x900 flags 0
(XEN) [ 3.548558] AMD-Vi: Dev_Id Range: 0x900 -> 0x907
(XEN) [ 3.569345] AMD-Vi: IVHD Device Entry: type 0x2 id 0x60 flags 0
(XEN) [ 3.593757] AMD-Vi: IVHD Device Entry: type 0x2 id 0x500 flags 0
(XEN) [ 3.618430] AMD-Vi: IVHD Device Entry: type 0x2 id 0x608 flags 0
(XEN) [ 3.643142] AMD-Vi: IVHD Device Entry: type 0x2 id 0x800 flags 0
(XEN) [ 3.667880] AMD-Vi: IVHD Device Entry: type 0x2 id 0x610 flags 0
(XEN) [ 3.692657] AMD-Vi: IVHD Device Entry: type 0x2 id 0x700 flags 0
(XEN) [ 3.717408] AMD-Vi: IVHD Device Entry: type 0x2 id 0x68 flags 0
(XEN) [ 3.741872] AMD-Vi: IVHD Device Entry: type 0x3 id 0x400 flags 0
(XEN) [ 3.766585] AMD-Vi: Dev_Id Range: 0x400 -> 0x407
(XEN) [ 3.787370] AMD-Vi: IVHD Device Entry: type 0x2 id 0x88 flags 0
(XEN) [ 3.811797] AMD-Vi: IVHD Device Entry: type 0x3 id 0x90 flags 0
(XEN) [ 3.836237] AMD-Vi: Dev_Id Range: 0x90 -> 0x92
(XEN) [ 3.856501] AMD-Vi: IVHD Device Entry: type 0x3 id 0x98 flags 0
(XEN) [ 3.880928] AMD-Vi: Dev_Id Range: 0x98 -> 0x9a
(XEN) [ 3.901143] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa0 flags 0xd7
(XEN) [ 3.926335] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa2 flags 0
(XEN) [ 3.950774] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa3 flags 0
(XEN) [ 3.975213] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa4 flags 0
(XEN) [ 3.999640] AMD-Vi: IVHD Device Entry: type 0x43 id 0x300 flags 0
(XEN) [ 4.024545] AMD-Vi: Dev_Id Range: 0x300 -> 0x3ff alias 0xa4
(XEN) [ 4.048205] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa5 flags 0
(XEN) [ 4.072591] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa8 flags 0
(XEN) [ 4.096954] AMD-Vi: IVHD Device Entry: type 0x2 id 0xa9 flags 0
(XEN) [ 4.121313] AMD-Vi: IVHD Device Entry: type 0x2 id 0x100 flags 0
(XEN) [ 4.145935] AMD-Vi: IVHD Device Entry: type 0x3 id 0xb0 flags 0
(XEN) [ 4.170322] AMD-Vi: Dev_Id Range: 0xb0 -> 0xb2
(XEN) [ 4.190562] AMD-Vi: IVHD Device Entry: type 0 id 0 flags 0
(XEN) [ 4.213715] AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
(XEN) [ 4.238439] AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
(XEN) [ 4.263983] AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
(XEN) [ 4.287981] AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
(XEN) [ 4.314189] AMD-Vi: Disabled HAP memory map sharing with IOMMU
(XEN) [ 4.338497] AMD-Vi: IOMMU 0 Enabled.
(XEN) [ 4.356110] I/O virtualisation enabled
(XEN) [ 4.374114] - Dom0 mode: Relaxed
(XEN) [ 4.390768] Interrupt remapping enabled
(XEN) [ 4.408942] nr_sockets: 1
(XEN) [ 4.423696] ENABLING IO-APIC IRQs
(XEN) [ 4.440296] -> Using new ACK method
(XEN) [ 4.457883] ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) [2019-10-30 22:04:11.424] HVM: ASIDs enabled.
(XEN) [2019-10-30 22:04:11.430] SVM: Supported advanced features:
(XEN) [2019-10-30 22:04:11.436] - Nested Page Tables (NPT)
(XEN) [2019-10-30 22:04:11.442] - Last Branch Record (LBR) Virtualisation
(XEN) [2019-10-30 22:04:11.448] - Next-RIP Saved on #VMEXIT
(XEN) [2019-10-30 22:04:11.454] - Pause-Intercept Filter
(XEN) [2019-10-30 22:04:11.460] HVM: SVM enabled
(XEN) [2019-10-30 22:04:11.466] HVM: Hardware Assisted Paging (HAP) detected
(XEN) [2019-10-30 22:04:11.472] HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) [2019-10-30 22:04:11.479] alt table ffff82d08047a1b0 -> ffff82d0804882f2
(XEN) [2019-10-30 22:04:06.313] microcode: CPU1 updated from revision 0x10000bf to 0x10000dc
(XEN) [2019-10-30 22:04:06.313] microcode: CPU2 updated from revision 0x10000bf to 0x10000dc
(XEN) [2019-10-30 22:04:06.313] microcode: CPU3 updated from revision 0x10000bf to 0x10000dc
(XEN) [2019-10-30 22:04:06.313] microcode: CPU4 updated from revision 0x10000bf to 0x10000dc
(XEN) [2019-10-30 22:04:06.313] microcode: CPU5 updated from revision 0x10000bf to 0x10000dc
(XEN) [2019-10-30 22:04:11.568] Brought up 6 CPUs
(XEN) [2019-10-30 22:04:11.581] Adding cpu 0 to runqueue 0
(XEN) [2019-10-30 22:04:11.587] First cpu on runqueue, activating
(XEN) [2019-10-30 22:04:11.593] Adding cpu 1 to runqueue 0
(XEN) [2019-10-30 22:04:11.598] Adding cpu 2 to runqueue 0
(XEN) [2019-10-30 22:04:11.604] Adding cpu 3 to runqueue 0
(XEN) [2019-10-30 22:04:11.610] Adding cpu 4 to runqueue 0
(XEN) [2019-10-30 22:04:11.616] Adding cpu 5 to runqueue 0
(XEN) [2019-10-30 22:04:11.622] Running stub recovery selftests...
(XEN) [2019-10-30 22:04:11.628] traps.c:1589: GPF (0000): ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d08038c3fc
(XEN) [2019-10-30 22:04:11.634] traps.c:784: Trap 12: ffff82d0bffff040 [ffff82d0bffff040] -> ffff82d08038c3fc
(XEN) [2019-10-30 22:04:11.640] traps.c:1123: Trap 3: ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d08038c3fc
(XEN) [2019-10-30 22:04:11.666] MCA: Use hw thresholding to adjust polling frequency
(XEN) [2019-10-30 22:04:11.672] mcheck_poll: Machine check polling timer started.
(XEN) [2019-10-30 22:04:11.679] Xenoprofile: Failed to setup IBS LVT offset, IBSCTL = 0xffffffff
(XEN) [2019-10-30 22:04:11.686] Dom0 has maximum 632 PIRQs
(XEN) [2019-10-30 22:04:11.692] Multiple initrd candidates, picking module #1
(XEN) [2019-10-30 22:04:11.698] NX (Execute Disable) protection active
(XEN) [2019-10-30 22:04:11.705] *** Building a PV Dom0 ***
(XEN) [2019-10-30 22:04:11.992] ELF: phdr: paddr=0x1000000 memsz=0x1b9e000
(XEN) [2019-10-30 22:04:11.999] ELF: phdr: paddr=0x2c00000 memsz=0x77c000
(XEN) [2019-10-30 22:04:12.005] ELF: phdr: paddr=0x337c000 memsz=0x2a358
(XEN) [2019-10-30 22:04:12.012] ELF: phdr: paddr=0x33a7000 memsz=0x47f000
(XEN) [2019-10-30 22:04:12.019] ELF: memory: 0x1000000 -> 0x3826000
(XEN) [2019-10-30 22:04:12.026] ELF: note: GUEST_OS = "linux"
(XEN) [2019-10-30 22:04:12.033] ELF: note: GUEST_VERSION = "2.6"
(XEN) [2019-10-30 22:04:12.040] ELF: note: XEN_VERSION = "xen-3.0"
(XEN) [2019-10-30 22:04:12.047] ELF: note: VIRT_BASE = 0xffffffff80000000
(XEN) [2019-10-30 22:04:12.054] ELF: note: INIT_P2M = 0x8000000000
(XEN) [2019-10-30 22:04:12.060] ELF: note: ENTRY = 0xffffffff833a7180
(XEN) [2019-10-30 22:04:12.067] ELF: note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) [2019-10-30 22:04:12.074] ELF: note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) [2019-10-30 22:04:12.081] ELF: note: SUPPORTED_FEATURES = 0x8801
(XEN) [2019-10-30 22:04:12.088] ELF: note: PAE_MODE = "yes"
(XEN) [2019-10-30 22:04:12.095] ELF: note: LOADER = "generic"
(XEN) [2019-10-30 22:04:12.102] ELF: note: unknown (0xd)
(XEN) [2019-10-30 22:04:12.109] ELF: note: SUSPEND_CANCEL = 0x1
(XEN) [2019-10-30 22:04:12.116] ELF: note: MOD_START_PFN = 0x1
(XEN) [2019-10-30 22:04:12.122] ELF: note: HV_START_LOW = 0xffff800000000000
(XEN) [2019-10-30 22:04:12.129] ELF: note: PADDR_OFFSET = 0
(XEN) [2019-10-30 22:04:12.136] ELF: note: PHYS32_ENTRY = 0x1000420
(XEN) [2019-10-30 22:04:12.143] ELF: Found PVH image
(XEN) [2019-10-30 22:04:12.150] ELF: addresses:
(XEN) [2019-10-30 22:04:12.156] virt_base = 0xffffffff80000000
(XEN) [2019-10-30 22:04:12.163] elf_paddr_offset = 0x0
(XEN) [2019-10-30 22:04:12.170] virt_offset = 0xffffffff80000000
(XEN) [2019-10-30 22:04:12.177] virt_kstart = 0xffffffff81000000
(XEN) [2019-10-30 22:04:12.184] virt_kend = 0xffffffff83826000
(XEN) [2019-10-30 22:04:12.191] virt_entry = 0xffffffff833a7180
(XEN) [2019-10-30 22:04:12.198] p2m_base = 0x8000000000
(XEN) [2019-10-30 22:04:12.205] Xen kernel: 64-bit, lsb, compat32
(XEN) [2019-10-30 22:04:12.212] Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x3826000
(XEN) [2019-10-30 22:04:12.221] PHYSICAL MEMORY ARRANGEMENT:
(XEN) [2019-10-30 22:04:12.228] Dom0 alloc.: 000000051c000000->0000000520000000 (497450 pages to be allocated)
(XEN) [2019-10-30 22:04:12.235] Init. ramdisk: 0000000535726000->0000000537ffb955
(XEN) [2019-10-30 22:04:12.243] VIRTUAL MEMORY ARRANGEMENT:
(XEN) [2019-10-30 22:04:12.250] Loaded kernel: ffffffff81000000->ffffffff83826000
(XEN) [2019-10-30 22:04:12.257] Init. ramdisk: 0000000000000000->0000000000000000
(XEN) [2019-10-30 22:04:12.265] Phys-Mach map: 0000008000000000->0000008000400000
(XEN) [2019-10-30 22:04:12.272] Start info: ffffffff83826000->ffffffff838264b8
(XEN) [2019-10-30 22:04:12.279] Xenstore ring: 0000000000000000->0000000000000000
(XEN) [2019-10-30 22:04:12.286] Console ring: 0000000000000000->0000000000000000
(XEN) [2019-10-30 22:04:12.294] Page tables: ffffffff83827000->ffffffff83848000
(XEN) [2019-10-30 22:04:12.301] Boot stack: ffffffff83848000->ffffffff83849000
(XEN) [2019-10-30 22:04:12.308] TOTAL: ffffffff80000000->ffffffff83c00000
(XEN) [2019-10-30 22:04:12.315] ENTRY ADDRESS: ffffffff833a7180
(XEN) [2019-10-30 22:04:12.324] Dom0 has maximum 6 VCPUs
(XEN) [2019-10-30 22:04:12.331] ELF: phdr 0 at 0xffffffff81000000 -> 0xffffffff82b9e000
(XEN) [2019-10-30 22:04:12.360] ELF: phdr 1 at 0xffffffff82c00000 -> 0xffffffff8337c000
(XEN) [2019-10-30 22:04:12.374] ELF: phdr 2 at 0xffffffff8337c000 -> 0xffffffff833a6358
(XEN) [2019-10-30 22:04:12.382] ELF: phdr 3 at 0xffffffff833a7000 -> 0xffffffff8351a000
(XEN) [2019-10-30 22:04:13.675] AMD-Vi: Setup I/O page table: device id = 0, type = 0x6, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.683] AMD-Vi: Setup I/O page table: device id = 0x10, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.690] AMD-Vi: Setup I/O page table: device id = 0x18, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.698] AMD-Vi: Setup I/O page table: device id = 0x28, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.706] AMD-Vi: Setup I/O page table: device id = 0x30, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.714] AMD-Vi: Setup I/O page table: device id = 0x48, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.722] AMD-Vi: Setup I/O page table: device id = 0x50, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.730] AMD-Vi: Setup I/O page table: device id = 0x60, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.739] AMD-Vi: Setup I/O page table: device id = 0x68, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.747] AMD-Vi: Setup I/O page table: device id = 0x88, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.756] AMD-Vi: Setup I/O page table: device id = 0x90, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.764] AMD-Vi: Setup I/O page table: device id = 0x92, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.773] AMD-Vi: Setup I/O page table: device id = 0x98, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.782] AMD-Vi: Setup I/O page table: device id = 0x9a, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.791] AMD-Vi: Setup I/O page table: device id = 0xa0, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.800] AMD-Vi: Setup I/O page table: device id = 0xa2, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.809] AMD-Vi: Setup I/O page table: device id = 0xa3, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.819] AMD-Vi: Setup I/O page table: device id = 0xa4, type = 0x5, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.828] AMD-Vi: Setup I/O page table: device id = 0xa5, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.838] AMD-Vi: Setup I/O page table: device id = 0xa8, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.848] AMD-Vi: Setup I/O page table: device id = 0xb0, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.858] AMD-Vi: Setup I/O page table: device id = 0xb2, type = 0x7, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.868] AMD-Vi: Skipping host bridge 0000:00:18.0
(XEN) [2019-10-30 22:04:13.877] AMD-Vi: Skipping host bridge 0000:00:18.1
(XEN) [2019-10-30 22:04:13.887] AMD-Vi: Skipping host bridge 0000:00:18.2
(XEN) [2019-10-30 22:04:13.897] AMD-Vi: Skipping host bridge 0000:00:18.3
(XEN) [2019-10-30 22:04:13.907] AMD-Vi: Skipping host bridge 0000:00:18.4
(XEN) [2019-10-30 22:04:13.917] AMD-Vi: Setup I/O page table: device id = 0x400, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.927] AMD-Vi: Setup I/O page table: device id = 0x401, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.937] AMD-Vi: Setup I/O page table: device id = 0x402, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.948] AMD-Vi: Setup I/O page table: device id = 0x403, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.958] AMD-Vi: Setup I/O page table: device id = 0x404, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.969] AMD-Vi: Setup I/O page table: device id = 0x405, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.980] AMD-Vi: Setup I/O page table: device id = 0x406, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:13.991] AMD-Vi: Setup I/O page table: device id = 0x407, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.002] AMD-Vi: Setup I/O page table: device id = 0x500, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.013] AMD-Vi: Setup I/O page table: device id = 0x608, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.025] AMD-Vi: Setup I/O page table: device id = 0x610, type = 0x2, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.036] AMD-Vi: Setup I/O page table: device id = 0x700, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.048] AMD-Vi: Setup I/O page table: device id = 0x800, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.060] AMD-Vi: Setup I/O page table: device id = 0x900, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.072] AMD-Vi: Setup I/O page table: device id = 0x901, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.084] AMD-Vi: Setup I/O page table: device id = 0x902, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.096] AMD-Vi: Setup I/O page table: device id = 0x903, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.108] AMD-Vi: Setup I/O page table: device id = 0x904, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.120] AMD-Vi: Setup I/O page table: device id = 0x905, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.133] AMD-Vi: Setup I/O page table: device id = 0x906, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.145] AMD-Vi: Setup I/O page table: device id = 0x907, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.158] AMD-Vi: Setup I/O page table: device id = 0xa00, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.170] AMD-Vi: Setup I/O page table: device id = 0xb00, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.183] AMD-Vi: Setup I/O page table: device id = 0xc00, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.196] AMD-Vi: Setup I/O page table: device id = 0xd00, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.209] AMD-Vi: Setup I/O page table: device id = 0xe00, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.222] AMD-Vi: Setup I/O page table: device id = 0xe01, type = 0x1, root table = 0x535724000, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:04:14.241] Initial low memory virq threshold set at 0x4000 pages.
(XEN) [2019-10-30 22:04:14.254] Scrubbing Free RAM in background
(XEN) [2019-10-30 22:04:14.267] Std. Loglevel: All
(XEN) [2019-10-30 22:04:14.280] Guest Loglevel: All
(XEN) [2019-10-30 22:04:14.293] Xen is relinquishing VGA console.
(XEN) [2019-10-30 22:04:14.390] *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) [2019-10-30 22:04:14.390] Freed 544kB init memory
(XEN) [2019-10-30 22:04:15.117] PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) [2019-10-30 22:04:15.117] PCI add device 0000:00:00.0
(XEN) [2019-10-30 22:04:15.117] PCI add device 0000:00:00.2
(XEN) [2019-10-30 22:04:15.117] PCI add device 0000:00:02.0
(XEN) [2019-10-30 22:04:15.118] PCI add device 0000:00:03.0
(XEN) [2019-10-30 22:04:15.118] PCI add device 0000:00:05.0
(XEN) [2019-10-30 22:04:15.118] PCI add device 0000:00:06.0
(XEN) [2019-10-30 22:04:15.119] PCI add device 0000:00:09.0
(XEN) [2019-10-30 22:04:15.119] PCI add device 0000:00:0a.0
(XEN) [2019-10-30 22:04:15.119] PCI add device 0000:00:0c.0
(XEN) [2019-10-30 22:04:15.120] PCI add device 0000:00:0d.0
(XEN) [2019-10-30 22:04:15.120] PCI add device 0000:00:11.0
(XEN) [2019-10-30 22:04:15.120] PCI add device 0000:00:12.0
(XEN) [2019-10-30 22:04:15.121] PCI add device 0000:00:12.2
(XEN) [2019-10-30 22:04:15.121] PCI add device 0000:00:13.0
(XEN) [2019-10-30 22:04:15.121] PCI add device 0000:00:13.2
(XEN) [2019-10-30 22:04:15.121] PCI add device 0000:00:14.0
(XEN) [2019-10-30 22:04:15.122] PCI add device 0000:00:14.2
(XEN) [2019-10-30 22:04:15.122] PCI add device 0000:00:14.3
(XEN) [2019-10-30 22:04:15.122] PCI add device 0000:00:14.4
(XEN) [2019-10-30 22:04:15.122] PCI add device 0000:00:14.5
(XEN) [2019-10-30 22:04:15.123] PCI add device 0000:00:15.0
(XEN) [2019-10-30 22:04:15.123] PCI add device 0000:00:16.0
(XEN) [2019-10-30 22:04:15.123] PCI add device 0000:00:16.2
(XEN) [2019-10-30 22:04:15.123] PCI add device 0000:00:18.0
(XEN) [2019-10-30 22:04:15.124] PCI add device 0000:00:18.1
(XEN) [2019-10-30 22:04:15.124] PCI add device 0000:00:18.2
(XEN) [2019-10-30 22:04:15.124] PCI add device 0000:00:18.3
(XEN) [2019-10-30 22:04:15.124] PCI add device 0000:00:18.4
(XEN) [2019-10-30 22:04:15.124] PCI add device 0000:0e:00.0
(XEN) [2019-10-30 22:04:15.125] PCI add device 0000:0e:00.1
(XEN) [2019-10-30 22:04:15.137] PCI add device 0000:0d:00.0
(XEN) [2019-10-30 22:04:15.147] PCI add device 0000:0c:00.0
(XEN) [2019-10-30 22:04:15.157] PCI add device 0000:0b:00.0
(XEN) [2019-10-30 22:04:15.167] PCI add device 0000:0a:00.0
(XEN) [2019-10-30 22:04:15.178] PCI add device 0000:09:00.0
(XEN) [2019-10-30 22:04:15.178] PCI add device 0000:09:00.1
(XEN) [2019-10-30 22:04:15.178] PCI add device 0000:09:00.2
(XEN) [2019-10-30 22:04:15.179] PCI add device 0000:09:00.3
(XEN) [2019-10-30 22:04:15.179] PCI add device 0000:09:00.4
(XEN) [2019-10-30 22:04:15.179] PCI add device 0000:09:00.5
(XEN) [2019-10-30 22:04:15.180] PCI add device 0000:09:00.6
(XEN) [2019-10-30 22:04:15.180] PCI add device 0000:09:00.7
(XEN) [2019-10-30 22:04:15.181] PCI add device 0000:05:00.0
(XEN) [2019-10-30 22:04:15.181] PCI add device 0000:06:01.0
(XEN) [2019-10-30 22:04:15.181] PCI add device 0000:06:02.0
(XEN) [2019-10-30 22:04:15.182] PCI add device 0000:08:00.0
(XEN) [2019-10-30 22:04:15.182] PCI add device 0000:07:00.0
(XEN) [2019-10-30 22:04:15.183] PCI add device 0000:04:00.0
(XEN) [2019-10-30 22:04:15.183] PCI add device 0000:04:00.1
(XEN) [2019-10-30 22:04:15.184] PCI add device 0000:04:00.2
(XEN) [2019-10-30 22:04:15.184] PCI add device 0000:04:00.3
(XEN) [2019-10-30 22:04:15.184] PCI add device 0000:04:00.4
(XEN) [2019-10-30 22:04:15.185] PCI add device 0000:04:00.5
(XEN) [2019-10-30 22:04:15.185] PCI add device 0000:04:00.6
(XEN) [2019-10-30 22:04:15.186] PCI add device 0000:04:00.7
(XEN) [2019-10-30 22:04:20.095] d0: Forcing read-only access to MFN fed00
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: CPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: CPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: CPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: CPU
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: PIC
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: IOAPIC
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: LAPIC
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: LAPIC
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: LAPIC
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: LAPIC
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: PCI_IRQ
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: ISA_IRQ
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: PCI_LINK
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: PIT
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: RTC
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: HPET
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: PMTIMER
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: MTRR
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: MTRR
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: MTRR
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: MTRR
(XEN) [2019-10-30 22:06:14.677] HVM d1 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:14.677] HVM d1v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:14.677] HVM d1v1 save: CPU_MSR
(XEN) [2019-10-30 22:06:14.677] HVM d1v2 save: CPU_MSR
(XEN) [2019-10-30 22:06:14.677] HVM d1v3 save: CPU_MSR
(XEN) [2019-10-30 22:06:14.677] HVM1 restore: MTRR 0
(XEN) [2019-10-30 22:06:14.677] HVM1 restore: MTRR 1
(XEN) [2019-10-30 22:06:14.677] HVM1 restore: MTRR 2
(XEN) [2019-10-30 22:06:14.678] HVM1 restore: MTRR 3
(XEN) [2019-10-30 22:06:14.678] HVM1 restore: CPU 0
(XEN) [2019-10-30 22:06:15.800] Dom1 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:06:17.286] grant_table.c:1786:d1v1 Expanding d1 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:06:17.286] grant_table.c:1786:d1v1 Expanding d1 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:06:17.286] grant_table.c:1786:d1v1 Expanding d1 grant table from 3 to 4 frames
(XEN) [2019-10-30 22:06:17.286] grant_table.c:1786:d1v1 Expanding d1 grant table from 4 to 5 frames
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: CPU
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: PIC
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: IOAPIC
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: LAPIC
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: PCI_IRQ
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: ISA_IRQ
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: PCI_LINK
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: PIT
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: RTC
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: HPET
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: PMTIMER
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: MTRR
(XEN) [2019-10-30 22:06:21.159] HVM d2 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:21.159] HVM d2v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:21.159] HVM2 restore: MTRR 0
(XEN) [2019-10-30 22:06:21.159] HVM2 restore: CPU 0
(XEN) [2019-10-30 22:06:22.108] Dom2 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:06:23.237] grant_table.c:1786:d2v0 Expanding d2 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:06:23.890] grant_table.c:1786:d1v0 Expanding d1 grant table from 5 to 6 frames
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: CPU
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: CPU
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: PIC
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: IOAPIC
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: LAPIC
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: LAPIC
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: PCI_IRQ
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: ISA_IRQ
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: PCI_LINK
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: PIT
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: RTC
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: HPET
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: PMTIMER
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: MTRR
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: MTRR
(XEN) [2019-10-30 22:06:27.382] HVM d3 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:27.382] HVM d3v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:27.382] HVM d3v1 save: CPU_MSR
(XEN) [2019-10-30 22:06:27.382] HVM3 restore: MTRR 0
(XEN) [2019-10-30 22:06:27.382] HVM3 restore: MTRR 1
(XEN) [2019-10-30 22:06:27.382] HVM3 restore: CPU 0
(XEN) [2019-10-30 22:06:28.085] Dom3 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:06:29.358] grant_table.c:1786:d3v0 Expanding d3 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:06:29.358] grant_table.c:1786:d3v0 Expanding d3 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: CPU
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: CPU
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: PIC
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: IOAPIC
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: LAPIC
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: LAPIC
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: PCI_IRQ
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: ISA_IRQ
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: PCI_LINK
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: PIT
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: RTC
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: HPET
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: PMTIMER
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: MTRR
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: MTRR
(XEN) [2019-10-30 22:06:33.629] HVM d4 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:33.629] HVM d4v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:33.629] HVM d4v1 save: CPU_MSR
(XEN) [2019-10-30 22:06:33.629] HVM4 restore: MTRR 0
(XEN) [2019-10-30 22:06:33.629] HVM4 restore: MTRR 1
(XEN) [2019-10-30 22:06:33.629] HVM4 restore: CPU 0
(XEN) [2019-10-30 22:06:34.388] Dom4 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:06:35.540] grant_table.c:1786:d4v0 Expanding d4 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:06:35.540] grant_table.c:1786:d4v0 Expanding d4 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: CPU
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: PIC
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: IOAPIC
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: LAPIC
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: PCI_IRQ
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: ISA_IRQ
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: PCI_LINK
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: PIT
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: RTC
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: HPET
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: PMTIMER
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: MTRR
(XEN) [2019-10-30 22:06:39.828] HVM d5 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:39.828] HVM d5v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:39.828] HVM5 restore: MTRR 0
(XEN) [2019-10-30 22:06:39.828] HVM5 restore: CPU 0
(XEN) [2019-10-30 22:06:40.639] Dom5 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:06:41.602] grant_table.c:1786:d5v0 Expanding d5 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: CPU
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: PIC
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: IOAPIC
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: LAPIC
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: PCI_IRQ
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: ISA_IRQ
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: PCI_LINK
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: PIT
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: RTC
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: HPET
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: PMTIMER
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: MTRR
(XEN) [2019-10-30 22:06:46.112] HVM d6 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:46.112] HVM d6v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:46.112] HVM6 restore: MTRR 0
(XEN) [2019-10-30 22:06:46.112] HVM6 restore: CPU 0
(XEN) [2019-10-30 22:06:46.898] Dom6 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:06:47.799] grant_table.c:1786:d6v0 Expanding d6 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: CPU
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: CPU
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: PIC
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: IOAPIC
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: LAPIC
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: LAPIC
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: PCI_IRQ
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: ISA_IRQ
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: PCI_LINK
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: PIT
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: RTC
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: HPET
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: PMTIMER
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: MTRR
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: MTRR
(XEN) [2019-10-30 22:06:52.386] HVM d7 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:52.386] HVM d7v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:52.386] HVM d7v1 save: CPU_MSR
(XEN) [2019-10-30 22:06:52.386] HVM7 restore: MTRR 0
(XEN) [2019-10-30 22:06:52.386] HVM7 restore: MTRR 1
(XEN) [2019-10-30 22:06:52.386] HVM7 restore: CPU 0
(XEN) [2019-10-30 22:06:53.720] Dom7 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:06:55.196] grant_table.c:1786:d7v0 Expanding d7 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:06:55.197] grant_table.c:1786:d7v0 Expanding d7 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:06:57.871] grant_table.c:1786:d1v2 Expanding d1 grant table from 6 to 7 frames
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: CPU
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: CPU
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: PIC
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: IOAPIC
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: LAPIC
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: LAPIC
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: PCI_IRQ
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: ISA_IRQ
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: PCI_LINK
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: PIT
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: RTC
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: HPET
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: PMTIMER
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: MTRR
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: MTRR
(XEN) [2019-10-30 22:06:59.277] HVM d8 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:06:59.277] HVM d8v0 save: CPU_MSR
(XEN) [2019-10-30 22:06:59.277] HVM d8v1 save: CPU_MSR
(XEN) [2019-10-30 22:06:59.277] HVM8 restore: MTRR 0
(XEN) [2019-10-30 22:06:59.277] HVM8 restore: MTRR 1
(XEN) [2019-10-30 22:06:59.277] HVM8 restore: CPU 0
(XEN) [2019-10-30 22:07:00.525] Dom8 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:07:01.826] grant_table.c:1786:d8v0 Expanding d8 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:07:01.826] grant_table.c:1786:d8v0 Expanding d8 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:07:05.748] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
(XEN) [2019-10-30 22:07:05.748] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
(XEN) [2019-10-30 22:07:05.748] CPU: 1
(XEN) [2019-10-30 22:07:05.748] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:05.748] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v2)
(XEN) [2019-10-30 22:07:05.748] rax: ffff830523f9ffff rbx: ffff82e004905f00 rcx: 0000000000000000
(XEN) [2019-10-30 22:07:05.748] rdx: 0000000000000001 rsi: 000000000000000a rdi: ffff82d0804a0698
(XEN) [2019-10-30 22:07:05.748] rbp: ffff830523f9f848 rsp: ffff830523f9f808 r8: ffff8305320a0000
(XEN) [2019-10-30 22:07:05.748] r9: 0000000000000038 r10: 0000000000000002 r11: 000000000000000a
(XEN) [2019-10-30 22:07:05.748] r12: ffff82e004905f00 r13: 0000000000000003 r14: 0000000000000003
(XEN) [2019-10-30 22:07:05.748] r15: ffff83041fb83000 cr0: 0000000080050033 cr4: 00000000000006e0
(XEN) [2019-10-30 22:07:05.748] cr3: 000000040a58d000 cr2: ffff8880604835a0
(XEN) [2019-10-30 22:07:05.748] fsb: 00007f4b8f899bc0 gsb: ffff88807d480000 gss: 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) [2019-10-30 22:07:05.748] Xen code around <ffff82d080265748> (iommu_map.c#update_paging_mode+0x1f2/0x3eb):
(XEN) [2019-10-30 22:07:05.748] 3d 3b 7b 22 00 00 75 07 <0f> 0b e9 c2 01 00 00 48 8d 35 1a ce 13 00 48 8d
(XEN) [2019-10-30 22:07:05.748] Xen stack trace from rsp=ffff830523f9f808:
(XEN) [2019-10-30 22:07:05.748] ffff82e00a6bc6e0 ffff82e00a6bc6e0 ffff83041fb83000 ffff83041fb83000
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83148 00000000000feff8 ffff83041fb83150 ffff830523f9f93c
(XEN) [2019-10-30 22:07:05.748] ffff830523f9f8c8 ffff82d080265ded 0000000380240580 00000000002482f9
(XEN) [2019-10-30 22:07:05.748] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83000 00000000000feff8 00000000000feff8 00000000002482f9
(XEN) [2019-10-30 22:07:05.748] ffff830523f9f928 ffff82d0802583b6 00000000000feff8 0000000000000001
(XEN) [2019-10-30 22:07:05.748] 00000003802405da 00000000002482f9 ffff830523f9f93c 0000000000000003
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83000 00000000000feff8 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ffff830523f9f960 ffff82d0802586fb 0000000048834780 0000000000000003
(XEN) [2019-10-30 22:07:05.748] 0000000000000000 ffff830248834780 00000000000feff8 ffff830523f9f9f8
(XEN) [2019-10-30 22:07:05.748] ffff82d08034a4a6 000000008038a845 0000000000000000 ffff820040024fc0
(XEN) [2019-10-30 22:07:05.748] ffff83041fb83000 00000000002482f9 0000000000000000 80000002484b5367
(XEN) [2019-10-30 22:07:05.748] ffff82004002d5a0 80000002484b5367 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:05.748] ffff820040024000 0000000000000000 00000000002482f9 00000000000feff8
(XEN) [2019-10-30 22:07:05.748] 0000000000000001 ffff830248834780 ffff830523f9fa50 ffff82d080342e13
(XEN) [2019-10-30 22:07:05.748] ffffffffffffffff 0000000000000007 ffff83041fb83000 0000000000000023
(XEN) [2019-10-30 22:07:05.748] 00000000002482fa ffff830248834780 0000000000000000 00000000002482f9
(XEN) [2019-10-30 22:07:05.748] 00000000000feff8 ffff830523f9fac8 ffff82d080343c52 0000000023f9fa78
(XEN) [2019-10-30 22:07:05.748] 0000000000000001 00000000002482f9 00000000000feff8 ffff830523f9fa98
(XEN) [2019-10-30 22:07:05.748] Xen call trace:
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
(XEN) [2019-10-30 22:07:05.748] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
(XEN) [2019-10-30 22:07:05.748] [<ffff82d0802221e8>] F do_memory_op+0x695/0x1bf7
(XEN) [2019-10-30 22:07:05.748] [<ffff82d080383601>] F pv_hypercall+0x2ca/0x537
(XEN) [2019-10-30 22:07:05.748] [<ffff82d08038a432>] F lstar_enter+0x112/0x120
(XEN) [2019-10-30 22:07:05.748]
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: CPU
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: CPU
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: PIC
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: IOAPIC
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: LAPIC
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: LAPIC
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: PCI_IRQ
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: ISA_IRQ
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: PCI_LINK
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: PIT
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: RTC
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: HPET
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: PMTIMER
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: MTRR
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: MTRR
(XEN) [2019-10-30 22:07:05.748] HVM d9 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:05.748] HVM d9v0 save: CPU_MSR
(XEN) [2019-10-30 22:07:05.748] HVM d9v1 save: CPU_MSR
(XEN) [2019-10-30 22:07:05.748] HVM9 restore: CPU 0
(XEN) [2019-10-30 22:07:06.696] d9: bind: m_gsi=16 g_gsi=36 dev=00.00.5 intx=0
(XEN) [2019-10-30 22:07:06.703] AMD-Vi: Disable: device id = 0xa2, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:06.703] AMD-Vi: Setup I/O page table: device id = 0xa2, type = 0x7, root table = 0x2482f8000, domain = 9, paging mode = 3
(XEN) [2019-10-30 22:07:06.703] AMD-Vi: Re-assign 0000:00:14.2 from dom0 to dom9
(d9) [2019-10-30 22:07:06.720] HVM Loader
(d9) [2019-10-30 22:07:06.720] Detected Xen v4.13.0-rc
(d9) [2019-10-30 22:07:06.720] Xenbus rings @0xfeffc000, event channel 1
(d9) [2019-10-30 22:07:06.720] System requested SeaBIOS
(d9) [2019-10-30 22:07:06.720] CPU speed is 3200 MHz
(d9) [2019-10-30 22:07:06.720] Relocating guest memory for lowmem MMIO space disabled
(XEN) [2019-10-30 22:07:06.728] irq.c:374: Dom9 PCI link 0 changed 0 -> 5
(d9) [2019-10-30 22:07:06.728] PCI-ISA link 0 routed to IRQ5
(XEN) [2019-10-30 22:07:06.735] irq.c:374: Dom9 PCI link 1 changed 0 -> 10
(d9) [2019-10-30 22:07:06.735] PCI-ISA link 1 routed to IRQ10
(XEN) [2019-10-30 22:07:06.740] irq.c:374: Dom9 PCI link 2 changed 0 -> 11
(d9) [2019-10-30 22:07:06.741] PCI-ISA link 2 routed to IRQ11
(XEN) [2019-10-30 22:07:06.745] irq.c:374: Dom9 PCI link 3 changed 0 -> 5
(d9) [2019-10-30 22:07:06.746] PCI-ISA link 3 routed to IRQ5
(d9) [2019-10-30 22:07:06.777] pci dev 01:3 INTA->IRQ10
(d9) [2019-10-30 22:07:06.779] pci dev 02:0 INTA->IRQ11
(d9) [2019-10-30 22:07:06.784] pci dev 04:0 INTA->IRQ5
(d9) [2019-10-30 22:07:06.787] pci dev 05:0 INTA->IRQ10
(d9) [2019-10-30 22:07:06.801] RAM in high memory; setting high_mem resource base to 100000000
(d9) [2019-10-30 22:07:06.802] pci dev 03:0 bar 10 size 002000000: 0f0000008
(d9) [2019-10-30 22:07:06.802] pci dev 02:0 bar 14 size 001000000: 0f2000008
(d9) [2019-10-30 22:07:06.803] pci dev 04:0 bar 30 size 000040000: 0f3000000
(d9) [2019-10-30 22:07:06.803] pci dev 03:0 bar 30 size 000010000: 0f3040000
(d9) [2019-10-30 22:07:06.803] pci dev 05:0 bar 10 size 000004000: 0f3050004
(XEN) [2019-10-30 22:07:06.804] memory_map:add: dom9 gfn=f3050 mfn=fdef8 nr=4
(d9) [2019-10-30 22:07:06.807] pci dev 03:0 bar 14 size 000001000: 0f3054000
(d9) [2019-10-30 22:07:06.807] pci dev 02:0 bar 10 size 000000100: 00000c001
(d9) [2019-10-30 22:07:06.808] pci dev 04:0 bar 10 size 000000100: 00000c101
(d9) [2019-10-30 22:07:06.809] pci dev 04:0 bar 14 size 000000100: 0f3055000
(d9) [2019-10-30 22:07:06.810] pci dev 01:1 bar 20 size 000000010: 00000c201
(d9) [2019-10-30 22:07:06.810] Multiprocessor initialisation:
(d9) [2019-10-30 22:07:06.812] - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d9) [2019-10-30 22:07:06.813] - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d9) [2019-10-30 22:07:06.813] Testing HVM environment:
(d9) [2019-10-30 22:07:06.813] Using scratch memory at 400000
(d9) [2019-10-30 22:07:06.827] - REP INSB across page boundaries ... passed
(d9) [2019-10-30 22:07:06.841] - REP INSW across page boundaries ... passed
(d9) [2019-10-30 22:07:06.854] - GS base MSRs and SWAPGS ... passed
(d9) [2019-10-30 22:07:06.854] Passed 3 of 3 tests
(d9) [2019-10-30 22:07:06.854] Writing SMBIOS tables ...
(d9) [2019-10-30 22:07:06.855] Loading SeaBIOS ...
(d9) [2019-10-30 22:07:06.855] Creating MP tables ...
(d9) [2019-10-30 22:07:06.856] Loading ACPI ...
(d9) [2019-10-30 22:07:06.856] vm86 TSS at fc00a980
(d9) [2019-10-30 22:07:06.857] BIOS map:
(d9) [2019-10-30 22:07:06.857] 10000-100e3: Scratch space
(d9) [2019-10-30 22:07:06.857] c0000-fffff: Main BIOS
(d9) [2019-10-30 22:07:06.857] E820 table:
(d9) [2019-10-30 22:07:06.857] [00]: 00000000:00000000 - 00000000:000a0000: RAM
(d9) [2019-10-30 22:07:06.857] HOLE: 00000000:000a0000 - 00000000:000c0000
(d9) [2019-10-30 22:07:06.857] [01]: 00000000:000c0000 - 00000000:00100000: RESERVED
(d9) [2019-10-30 22:07:06.857] [02]: 00000000:00100000 - 00000000:1f800000: RAM
(d9) [2019-10-30 22:07:06.857] HOLE: 00000000:1f800000 - 00000000:fc000000
(d9) [2019-10-30 22:07:06.857] [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d9) [2019-10-30 22:07:06.857] [04]: 00000001:00000000 - 00000001:00000000: RAM
(d9) [2019-10-30 22:07:06.857] Invoking SeaBIOS ...
(d9) [2019-10-30 22:07:06.857] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d9) [2019-10-30 22:07:06.857] BUILD: gcc: (Debian 8.3.0-6) 8.3.0 binutils: (GNU Binutils for Debian) 2.31.1
(d9) [2019-10-30 22:07:06.857]
(d9) [2019-10-30 22:07:06.858] Found Xen hypervisor signature at 40000000
(d9) [2019-10-30 22:07:06.858] Running on QEMU (i440fx)
(d9) [2019-10-30 22:07:06.858] xen: copy e820...
(d9) [2019-10-30 22:07:06.858] Relocating init from 0x000d8920 to 0x1f7ac480 (size 80608)
(d9) [2019-10-30 22:07:06.858] Found QEMU fw_cfg
(d9) [2019-10-30 22:07:06.859] RamSizeOver4G: 0x0000000000000000 [cmos]
(d9) [2019-10-30 22:07:06.860] boot order:
(d9) [2019-10-30 22:07:06.860] 1: /rom@genroms/linuxboot.bin
(d9) [2019-10-30 22:07:06.862] Found 8 PCI devices (max PCI bus is 00)
(d9) [2019-10-30 22:07:06.862] Allocated Xen hypercall page at 1f7ff000
(d9) [2019-10-30 22:07:06.863] Detected Xen v4.13.0-rc
(d9) [2019-10-30 22:07:06.863] xen: copy BIOS tables...
(d9) [2019-10-30 22:07:06.863] Copying SMBIOS entry point from 0x00010020 to 0x000f5be0
(d9) [2019-10-30 22:07:06.863] Copying MPTABLE from 0xfc001180/fc001190 to 0x000f5ae0
(d9) [2019-10-30 22:07:06.863] Copying PIR from 0x00010040 to 0x000f5a60
(d9) [2019-10-30 22:07:06.863] Copying ACPI RSDP from 0x000100c0 to 0x000f5a30
(d9) [2019-10-30 22:07:06.863] Using pmtimer, ioport 0xb008
(d9) [2019-10-30 22:07:06.863] Scan for VGA option rom
(d9) [2019-10-30 22:07:06.874] Running option rom at c000:0003
(XEN) [2019-10-30 22:07:06.874] stdvga.c:173:d9v0 entering stdvga mode
(d9) [2019-10-30 22:07:06.883] pmm call arg1=0
(d9) [2019-10-30 22:07:06.883] Turning on vga text mode console
(d9) [2019-10-30 22:07:06.926] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d9) [2019-10-30 22:07:06.930] Machine UUID e594f0d9-1acc-42d4-8c1f-7d23a4a2698d
(d9) [2019-10-30 22:07:06.931] ATA controller 1 at 1f0/3f4/c200 (irq 14 dev 9)
(d9) [2019-10-30 22:07:06.933] ATA controller 2 at 170/374/c208 (irq 15 dev 9)
(d9) [2019-10-30 22:07:06.934] Found 0 lpt ports
(d9) [2019-10-30 22:07:06.934] Found 0 serial ports
(d9) [2019-10-30 22:07:06.935] ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (5120 MiBytes)
(d9) [2019-10-30 22:07:06.935] Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(d9) [2019-10-30 22:07:06.936] PS2 keyboard initialized
(d9) [2019-10-30 22:07:06.936] All threads complete.
(d9) [2019-10-30 22:07:06.936] Scan for option roms
(d9) [2019-10-30 22:07:06.953] Running option rom at c980:0003
(d9) [2019-10-30 22:07:06.956] pmm call arg1=1
(d9) [2019-10-30 22:07:06.956] pmm call arg1=0
(d9) [2019-10-30 22:07:06.957] pmm call arg1=1
(d9) [2019-10-30 22:07:06.957] pmm call arg1=0
(d9) [2019-10-30 22:07:06.967] Running option rom at ca80:0003
(d9) [2019-10-30 22:07:06.967] Searching bootorder for: /pci@i0cf8/*@4
(d9) [2019-10-30 22:07:06.967] Searching bootorder for: /rom@genroms/linuxboot.bin
(d9) [2019-10-30 22:07:06.968] Searching bootorder for: HALT
(d9) [2019-10-30 22:07:06.968] drive 0x000f59c0: PCHS=10402/16/63 translation=lba LCHS=652/255/63 s=10485760
(d9) [2019-10-30 22:07:06.968] Space available for UMB: cb000-eb800, f5400-f59c0
(d9) [2019-10-30 22:07:06.968] Returned 258048 bytes of ZoneHigh
(d9) [2019-10-30 22:07:06.968] e820 map has 6 items:
(d9) [2019-10-30 22:07:06.968] 0: 0000000000000000 - 000000000009fc00 = 1 RAM
(d9) [2019-10-30 22:07:06.968] 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(d9) [2019-10-30 22:07:06.968] 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(d9) [2019-10-30 22:07:06.968] 3: 0000000000100000 - 000000001f7ff000 = 1 RAM
(d9) [2019-10-30 22:07:06.968] 4: 000000001f7ff000 - 000000001f800000 = 2 RESERVED
(d9) [2019-10-30 22:07:06.968] 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(d9) [2019-10-30 22:07:06.969] enter handle_19:
(d9) [2019-10-30 22:07:06.969] NULL
(d9) [2019-10-30 22:07:06.971] Booting from ROM...
(d9) [2019-10-30 22:07:06.971] Booting from ca80:003c
(XEN) [2019-10-30 22:07:06.977] grant_table.c:1786:d7v0 Expanding d7 grant table from 3 to 4 frames
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: CPU
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: CPU
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: PIC
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: IOAPIC
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: LAPIC
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: LAPIC
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: PCI_IRQ
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: ISA_IRQ
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: PCI_LINK
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: PIT
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: RTC
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: HPET
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: PMTIMER
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: MTRR
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: MTRR
(XEN) [2019-10-30 22:07:12.346] HVM d10 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:12.346] HVM d10v0 save: CPU_MSR
(XEN) [2019-10-30 22:07:12.346] HVM d10v1 save: CPU_MSR
(XEN) [2019-10-30 22:07:12.346] HVM10 restore: MTRR 0
(XEN) [2019-10-30 22:07:12.346] HVM10 restore: MTRR 1
(XEN) [2019-10-30 22:07:12.346] HVM10 restore: CPU 0
(XEN) [2019-10-30 22:07:13.090] Dom10 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:07:14.433] grant_table.c:1786:d10v0 Expanding d10 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:07:14.433] grant_table.c:1786:d10v0 Expanding d10 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:07:17.161] grant_table.c:1786:d7v0 Expanding d7 grant table from 4 to 5 frames
(XEN) [2019-10-30 22:07:18.176] grant_table.c:1786:d7v1 Expanding d7 grant table from 5 to 6 frames
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: CPU
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: PIC
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: IOAPIC
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: LAPIC
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: PCI_IRQ
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: ISA_IRQ
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: PCI_LINK
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: PIT
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: RTC
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: HPET
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: PMTIMER
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: MTRR
(XEN) [2019-10-30 22:07:18.508] HVM d11 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:18.508] HVM d11v0 save: CPU_MSR
(XEN) [2019-10-30 22:07:18.508] HVM11 restore: MTRR 0
(XEN) [2019-10-30 22:07:18.508] HVM11 restore: CPU 0
(XEN) [2019-10-30 22:07:19.271] Dom11 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:07:20.456] grant_table.c:1786:d11v0 Expanding d11 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:07:21.303] grant_table.c:1786:d11v0 Expanding d11 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:07:23.373] grant_table.c:1786:d7v0 Expanding d7 grant table from 6 to 7 frames
(XEN) [2019-10-30 22:07:23.548] grant_table.c:1786:d7v0 Expanding d7 grant table from 7 to 8 frames
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: CPU
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: CPU
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: PIC
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: IOAPIC
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: LAPIC
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: LAPIC
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: PCI_IRQ
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: ISA_IRQ
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: PCI_LINK
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: PIT
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: RTC
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: HPET
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: PMTIMER
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: MTRR
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: MTRR
(XEN) [2019-10-30 22:07:24.719] HVM d12 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:24.719] HVM d12v0 save: CPU_MSR
(XEN) [2019-10-30 22:07:24.719] HVM d12v1 save: CPU_MSR
(XEN) [2019-10-30 22:07:24.719] HVM12 restore: MTRR 0
(XEN) [2019-10-30 22:07:24.719] HVM12 restore: MTRR 1
(XEN) [2019-10-30 22:07:24.719] HVM12 restore: CPU 0
(XEN) [2019-10-30 22:07:25.759] Dom12 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:07:26.995] grant_table.c:1786:d12v0 Expanding d12 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:07:26.995] grant_table.c:1786:d12v0 Expanding d12 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:07:31.222] HVM d13v0 save: CPU
(XEN) [2019-10-30 22:07:31.222] HVM d13 save: PIC
(XEN) [2019-10-30 22:07:31.222] HVM d13 save: IOAPIC
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: LAPIC
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: PCI_IRQ
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: ISA_IRQ
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: PCI_LINK
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: PIT
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: RTC
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: HPET
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: PMTIMER
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: MTRR
(XEN) [2019-10-30 22:07:31.223] HVM d13 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:31.223] HVM d13v0 save: CPU_MSR
(XEN) [2019-10-30 22:07:31.223] HVM13 restore: MTRR 0
(XEN) [2019-10-30 22:07:31.223] HVM13 restore: CPU 0
(XEN) [2019-10-30 22:07:31.985] Dom13 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:07:32.813] grant_table.c:1786:d13v0 Expanding d13 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:07:37.246] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
(XEN) [2019-10-30 22:07:37.246] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
(XEN) [2019-10-30 22:07:37.246] CPU: 2
(XEN) [2019-10-30 22:07:37.246] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:37.246] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v4)
(XEN) [2019-10-30 22:07:37.246] rax: ffff830523f8ffff rbx: ffff82e007122c80 rcx: 0000000000000000
(XEN) [2019-10-30 22:07:37.246] rdx: 0000000000000002 rsi: 000000000000000a rdi: ffff82d0804a0698
(XEN) [2019-10-30 22:07:37.246] rbp: ffff830523f8f848 rsp: ffff830523f8f808 r8: ffff8305320a0000
(XEN) [2019-10-30 22:07:37.246] r9: 0000000000000036 r10: 0000000000000002 r11: 000000000000000a
(XEN) [2019-10-30 22:07:37.246] r12: ffff82e007122c80 r13: 0000000000000003 r14: 0000000000000001
(XEN) [2019-10-30 22:07:37.246] r15: ffff83042af84000 cr0: 0000000080050033 cr4: 00000000000006e0
(XEN) [2019-10-30 22:07:37.246] cr3: 000000041288f000 cr2: 00007f7a06908180
(XEN) [2019-10-30 22:07:37.246] fsb: 00007febf6eabbc0 gsb: ffff88807d500000 gss: 0000000000000000
(XEN) [2019-10-30 22:07:37.246] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) [2019-10-30 22:07:37.246] Xen code around <ffff82d080265748> (iommu_map.c#update_paging_mode+0x1f2/0x3eb):
(XEN) [2019-10-30 22:07:37.246] 3d 3b 7b 22 00 00 75 07 <0f> 0b e9 c2 01 00 00 48 8d 35 1a ce 13 00 48 8d
(XEN) [2019-10-30 22:07:37.246] Xen stack trace from rsp=ffff830523f8f808:
(XEN) [2019-10-30 22:07:37.246] ffff830523f8f848 0000000000000206 ffff83042af84000 ffff83042af84000
(XEN) [2019-10-30 22:07:37.246] ffff83042af84148 0000000000040000 ffff83042af84150 ffff830523f8f93c
(XEN) [2019-10-30 22:07:37.246] ffff830523f8f8c8 ffff82d080265ded 0000000323f8f8c8 0000000000100000
(XEN) [2019-10-30 22:07:37.246] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:37.246] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:37.246] ffff83042af84000 0000000000040000 0000000000040000 0000000000100000
(XEN) [2019-10-30 22:07:37.246] ffff830523f8f928 ffff82d0802583b6 0000000000040000 0000000000040000
(XEN) [2019-10-30 22:07:37.246] 00000003802405da 0000000000100000 ffff830523f8f93c 0000000000000003
(XEN) [2019-10-30 22:07:37.246] ffff83042af84000 0000000000040000 0000000000000012 0000000000000000
(XEN) [2019-10-30 22:07:37.246] ffff830523f8f960 ffff82d0802586fb 000000000e9dd840 0000000000000003
(XEN) [2019-10-30 22:07:37.246] 0000000000000000 ffff83040e9dd840 0000000000040000 ffff830523f8f9f8
(XEN) [2019-10-30 22:07:37.246] ffff82d08034a4a6 000000008038a845 ffffffffffffffff ffff820040009008
(XEN) [2019-10-30 22:07:37.246] ffff83042af84000 0000000000100000 0000001200000000 ffff82d08038a845
(XEN) [2019-10-30 22:07:37.246] ffff82d08038a851 ffff82d08038a845 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:37.246] ffff820040009000 0000000000000012 0000000000100000 0000000000040000
(XEN) [2019-10-30 22:07:37.246] 0000000000040000 ffff83040e9dd840 ffff830523f8fa50 ffff82d080342e13
(XEN) [2019-10-30 22:07:37.246] ffffffffffffffff 0000000000000007 ffff83042af84000 0000000000000023
(XEN) [2019-10-30 22:07:37.246] 0000000000140000 ffff83040e9dd840 0000000000000000 0000000000100000
(XEN) [2019-10-30 22:07:37.246] 0000000000040000 ffff830523f8fac8 ffff82d080343c52 000000008038a8ba
(XEN) [2019-10-30 22:07:37.246] 0000000000040000 0000000000100000 0000000000040000 ffff830523f8fa98
(XEN) [2019-10-30 22:07:37.246] Xen call trace:
(XEN) [2019-10-30 22:07:37.246] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:37.246] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
(XEN) [2019-10-30 22:07:37.246] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
(XEN) [2019-10-30 22:07:37.246] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
(XEN) [2019-10-30 22:07:37.246] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
(XEN) [2019-10-30 22:07:37.246] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
(XEN) [2019-10-30 22:07:37.246] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
(XEN) [2019-10-30 22:07:37.246] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
(XEN) [2019-10-30 22:07:37.246] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
(XEN) [2019-10-30 22:07:37.246] [<ffff82d0802221e8>] F do_memory_op+0x695/0x1bf7
(XEN) [2019-10-30 22:07:37.246] [<ffff82d080383601>] F pv_hypercall+0x2ca/0x537
(XEN) [2019-10-30 22:07:37.246] [<ffff82d08038a432>] F lstar_enter+0x112/0x120
(XEN) [2019-10-30 22:07:37.246]
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: CPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: CPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: CPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: CPU
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: PIC
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: IOAPIC
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: LAPIC
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: LAPIC
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: LAPIC
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: LAPIC
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: PCI_IRQ
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: ISA_IRQ
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: PCI_LINK
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: PIT
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: RTC
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: HPET
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: PMTIMER
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: MTRR
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: MTRR
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: MTRR
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: MTRR
(XEN) [2019-10-30 22:07:37.490] HVM d14 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:37.490] HVM d14v0 save: CPU_MSR
(XEN) [2019-10-30 22:07:37.490] HVM d14v1 save: CPU_MSR
(XEN) [2019-10-30 22:07:37.490] HVM d14v2 save: CPU_MSR
(XEN) [2019-10-30 22:07:37.490] HVM d14v3 save: CPU_MSR
(XEN) [2019-10-30 22:07:37.490] HVM14 restore: CPU 0
(XEN) [2019-10-30 22:07:41.329] d14: bind: m_gsi=37 g_gsi=36 dev=00.00.5 intx=0
(XEN) [2019-10-30 22:07:41.336] AMD-Vi: Disable: device id = 0x800, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:41.336] AMD-Vi: Setup I/O page table: device id = 0x800, type = 0x1, root table = 0x389164000, domain = 14, paging mode = 3
(XEN) [2019-10-30 22:07:41.336] AMD-Vi: Re-assign 0000:08:00.0 from dom0 to dom14
(d14) [2019-10-30 22:07:41.362] HVM Loader
(d14) [2019-10-30 22:07:41.362] Detected Xen v4.13.0-rc
(d14) [2019-10-30 22:07:41.362] Xenbus rings @0xfeffc000, event channel 1
(d14) [2019-10-30 22:07:41.362] System requested SeaBIOS
(d14) [2019-10-30 22:07:41.362] CPU speed is 3200 MHz
(d14) [2019-10-30 22:07:41.363] Relocating guest memory for lowmem MMIO space disabled
(XEN) [2019-10-30 22:07:41.370] irq.c:374: Dom14 PCI link 0 changed 0 -> 5
(d14) [2019-10-30 22:07:41.370] PCI-ISA link 0 routed to IRQ5
(XEN) [2019-10-30 22:07:41.377] irq.c:374: Dom14 PCI link 1 changed 0 -> 10
(d14) [2019-10-30 22:07:41.377] PCI-ISA link 1 routed to IRQ10
(XEN) [2019-10-30 22:07:41.384] irq.c:374: Dom14 PCI link 2 changed 0 -> 11
(d14) [2019-10-30 22:07:41.384] PCI-ISA link 2 routed to IRQ11
(XEN) [2019-10-30 22:07:41.391] irq.c:374: Dom14 PCI link 3 changed 0 -> 5
(d14) [2019-10-30 22:07:41.391] PCI-ISA link 3 routed to IRQ5
(d14) [2019-10-30 22:07:41.435] pci dev 01:3 INTA->IRQ10
(d14) [2019-10-30 22:07:41.438] pci dev 02:0 INTA->IRQ11
(d14) [2019-10-30 22:07:41.445] pci dev 04:0 INTA->IRQ5
(d14) [2019-10-30 22:07:41.449] pci dev 05:0 INTA->IRQ10
(d14) [2019-10-30 22:07:41.470] RAM in high memory; setting high_mem resource base to 10f800000
(d14) [2019-10-30 22:07:41.470] pci dev 03:0 bar 10 size 002000000: 0f0000008
(d14) [2019-10-30 22:07:41.471] pci dev 02:0 bar 14 size 001000000: 0f2000008
(d14) [2019-10-30 22:07:41.472] pci dev 04:0 bar 30 size 000040000: 0f3000000
(d14) [2019-10-30 22:07:41.473] pci dev 04:0 bar 10 size 000020000: 0f3040000
(d14) [2019-10-30 22:07:41.473] pci dev 03:0 bar 30 size 000010000: 0f3060000
(d14) [2019-10-30 22:07:41.473] pci dev 05:0 bar 10 size 000002000: 0f3070004
(XEN) [2019-10-30 22:07:41.474] memory_map:add: dom14 gfn=f3070 mfn=fe3fe nr=1
(d14) [2019-10-30 22:07:41.477] pci dev 03:0 bar 14 size 000001000: 0f3072000
(d14) [2019-10-30 22:07:41.477] pci dev 02:0 bar 10 size 000000100: 00000c001
(d14) [2019-10-30 22:07:41.478] pci dev 04:0 bar 14 size 000000040: 00000c101
(d14) [2019-10-30 22:07:41.479] pci dev 01:1 bar 20 size 000000010: 00000c141
(d14) [2019-10-30 22:07:41.480] Multiprocessor initialisation:
(d14) [2019-10-30 22:07:41.482] - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d14) [2019-10-30 22:07:41.484] - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d14) [2019-10-30 22:07:41.486] - CPU2 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d14) [2019-10-30 22:07:41.489] - CPU3 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d14) [2019-10-30 22:07:41.489] Testing HVM environment:
(d14) [2019-10-30 22:07:41.489] Using scratch memory at 400000
(d14) [2019-10-30 22:07:41.501] - REP INSB across page boundaries ... passed
(d14) [2019-10-30 22:07:41.514] - REP INSW across page boundaries ... passed
(d14) [2019-10-30 22:07:41.526] - GS base MSRs and SWAPGS ... passed
(d14) [2019-10-30 22:07:41.526] Passed 3 of 3 tests
(d14) [2019-10-30 22:07:41.526] Writing SMBIOS tables ...
(d14) [2019-10-30 22:07:41.527] Loading SeaBIOS ...
(d14) [2019-10-30 22:07:41.527] Creating MP tables ...
(d14) [2019-10-30 22:07:41.527] Loading ACPI ...
(d14) [2019-10-30 22:07:41.528] vm86 TSS at fc00aa00
(d14) [2019-10-30 22:07:41.529] BIOS map:
(d14) [2019-10-30 22:07:41.529] 10000-100e3: Scratch space
(d14) [2019-10-30 22:07:41.529] c0000-fffff: Main BIOS
(d14) [2019-10-30 22:07:41.529] E820 table:
(d14) [2019-10-30 22:07:41.529] [00]: 00000000:00000000 - 00000000:000a0000: RAM
(d14) [2019-10-30 22:07:41.529] HOLE: 00000000:000a0000 - 00000000:000c0000
(d14) [2019-10-30 22:07:41.529] [01]: 00000000:000c0000 - 00000000:00100000: RESERVED
(d14) [2019-10-30 22:07:41.529] [02]: 00000000:00100000 - 00000000:f0000000: RAM
(d14) [2019-10-30 22:07:41.529] HOLE: 00000000:f0000000 - 00000000:fc000000
(d14) [2019-10-30 22:07:41.529] [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d14) [2019-10-30 22:07:41.529] [04]: 00000001:00000000 - 00000001:0f800000: RAM
(d14) [2019-10-30 22:07:41.529] Invoking SeaBIOS ...
(d14) [2019-10-30 22:07:41.530] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d14) [2019-10-30 22:07:41.530] BUILD: gcc: (Debian 8.3.0-6) 8.3.0 binutils: (GNU Binutils for Debian) 2.31.1
(d14) [2019-10-30 22:07:41.530]
(d14) [2019-10-30 22:07:41.530] Found Xen hypervisor signature at 40000000
(d14) [2019-10-30 22:07:41.530] Running on QEMU (i440fx)
(d14) [2019-10-30 22:07:41.530] xen: copy e820...
(d14) [2019-10-30 22:07:41.530] Relocating init from 0x000d8920 to 0xeffac480 (size 80608)
(d14) [2019-10-30 22:07:41.530] Found QEMU fw_cfg
(d14) [2019-10-30 22:07:41.532] RamSizeOver4G: 0x000000000f800000 [cmos]
(d14) [2019-10-30 22:07:41.533] boot order:
(d14) [2019-10-30 22:07:41.533] 1: /rom@genroms/linuxboot.bin
(d14) [2019-10-30 22:07:41.536] Found 8 PCI devices (max PCI bus is 00)
(d14) [2019-10-30 22:07:41.536] Allocated Xen hypercall page at effff000
(d14) [2019-10-30 22:07:41.536] Detected Xen v4.13.0-rc
(d14) [2019-10-30 22:07:41.536] xen: copy BIOS tables...
(d14) [2019-10-30 22:07:41.536] Copying SMBIOS entry point from 0x00010020 to 0x000f5be0
(d14) [2019-10-30 22:07:41.536] Copying MPTABLE from 0xfc0011e0/fc0011f0 to 0x000f5ac0
(d14) [2019-10-30 22:07:41.536] Copying PIR from 0x00010040 to 0x000f5a40
(d14) [2019-10-30 22:07:41.536] Copying ACPI RSDP from 0x000100c0 to 0x000f5a10
(d14) [2019-10-30 22:07:41.536] Using pmtimer, ioport 0xb008
(d14) [2019-10-30 22:07:41.537] Scan for VGA option rom
(d14) [2019-10-30 22:07:41.550] Running option rom at c000:0003
(XEN) [2019-10-30 22:07:41.550] stdvga.c:173:d14v0 entering stdvga mode
(d14) [2019-10-30 22:07:41.561] pmm call arg1=0
(d14) [2019-10-30 22:07:41.561] Turning on vga text mode console
(d14) [2019-10-30 22:07:41.626] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d14) [2019-10-30 22:07:41.634] Machine UUID 27937ea6-1ca6-4339-9d44-252580d98ff5
(d14) [2019-10-30 22:07:41.634] XHCI init on dev 00:05.0: regs @ 0xf3070000, 4 ports, 32 slots, 32 byte contexts
(d14) [2019-10-30 22:07:41.634] XHCI extcap 0x1 @ 0xf3070500
(d14) [2019-10-30 22:07:41.634] XHCI protocol USB 3.00, 2 ports (offset 1), def 0
(d14) [2019-10-30 22:07:41.634] XHCI protocol USB 2.00, 2 ports (offset 3), def 0
(d14) [2019-10-30 22:07:41.636] ATA controller 1 at 1f0/3f4/c140 (irq 14 dev 9)
(d14) [2019-10-30 22:07:41.637] ATA controller 2 at 170/374/c148 (irq 15 dev 9)
(d14) [2019-10-30 22:07:41.637] Found 0 lpt ports
(d14) [2019-10-30 22:07:41.638] Found 1 serial ports
(d14) [2019-10-30 22:07:41.640] ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (10240 MiBytes)
(d14) [2019-10-30 22:07:41.640] Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(d14) [2019-10-30 22:07:41.641] ata0-1: QEMU HARDDISK ATA-7 Hard-Disk (800 GiBytes)
(d14) [2019-10-30 22:07:41.641] Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(d14) [2019-10-30 22:07:41.642] PS2 keyboard initialized
(d14) [2019-10-30 22:07:41.643] ata1-0: QEMU HARDDISK ATA-7 Hard-Disk (250 GiBytes)
(d14) [2019-10-30 22:07:41.643] Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(d14) [2019-10-30 22:07:41.644] ata1-1: QEMU HARDDISK ATA-7 Hard-Disk (260 GiBytes)
(d14) [2019-10-30 22:07:41.644] Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@1
(d14) [2019-10-30 22:07:41.761] XHCI port #4: 0x00200a03, powered, enabled, pls 0, speed 2 [Low]
(d14) [2019-10-30 22:07:41.791] XHCI no devices found
(d14) [2019-10-30 22:07:41.797] All threads complete.
(d14) [2019-10-30 22:07:41.797] Scan for option roms
(d14) [2019-10-30 22:07:41.820] Running option rom at c980:0003
(d14) [2019-10-30 22:07:41.826] pmm call arg1=1
(d14) [2019-10-30 22:07:41.826] pmm call arg1=0
(d14) [2019-10-30 22:07:41.827] pmm call arg1=1
(d14) [2019-10-30 22:07:41.828] pmm call arg1=0
(d14) [2019-10-30 22:07:41.845] Running option rom at ca80:0003
(d14) [2019-10-30 22:07:41.845] Searching bootorder for: /pci@i0cf8/*@4
(d14) [2019-10-30 22:07:41.845] Searching bootorder for: /rom@genroms/linuxboot.bin
(d14) [2019-10-30 22:07:41.845] Searching bootorder for: HALT
(d14) [2019-10-30 22:07:41.845] drive 0x000f59a0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=20971520
(d14) [2019-10-30 22:07:41.845] drive 0x000f5970: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=1677721600
(d14) [2019-10-30 22:07:41.845] drive 0x000f5940: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=524288000
(d14) [2019-10-30 22:07:41.846] drive 0x000f5910: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=545259520
(d14) [2019-10-30 22:07:41.846] Space available for UMB: cb000-eb800, f5400-f5910
(d14) [2019-10-30 22:07:41.846] Returned 253952 bytes of ZoneHigh
(d14) [2019-10-30 22:07:41.846] e820 map has 7 items:
(d14) [2019-10-30 22:07:41.846] 0: 0000000000000000 - 000000000009fc00 = 1 RAM
(d14) [2019-10-30 22:07:41.846] 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(d14) [2019-10-30 22:07:41.846] 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(d14) [2019-10-30 22:07:41.846] 3: 0000000000100000 - 00000000efffe000 = 1 RAM
(d14) [2019-10-30 22:07:41.846] 4: 00000000efffe000 - 00000000f0000000 = 2 RESERVED
(d14) [2019-10-30 22:07:41.846] 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(d14) [2019-10-30 22:07:41.846] 6: 0000000100000000 - 000000010f800000 = 1 RAM
(d14) [2019-10-30 22:07:41.847] enter handle_19:
(d14) [2019-10-30 22:07:41.847] NULL
(d14) [2019-10-30 22:07:41.851] Booting from ROM...
(d14) [2019-10-30 22:07:41.851] Booting from ca80:003c
(XEN) [2019-10-30 22:07:46.840] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
(XEN) [2019-10-30 22:07:46.840] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
(XEN) [2019-10-30 22:07:46.840] CPU: 3
(XEN) [2019-10-30 22:07:46.840] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:46.840] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v3)
(XEN) [2019-10-30 22:07:46.840] rax: ffff830523f7ffff rbx: ffff82e003409480 rcx: 0000000000000000
(XEN) [2019-10-30 22:07:46.840] rdx: 0000000000000003 rsi: 000000000000000a rdi: ffff82d0804a0698
(XEN) [2019-10-30 22:07:46.840] rbp: ffff830523f7f848 rsp: ffff830523f7f808 r8: ffff8305320a0000
(XEN) [2019-10-30 22:07:46.840] r9: 0000000000000030 r10: 0000000000000002 r11: 000000000000000a
(XEN) [2019-10-30 22:07:46.840] r12: ffff82e003409480 r13: 0000000000000003 r14: 0000000000000003
(XEN) [2019-10-30 22:07:46.840] r15: ffff8301b56e8000 cr0: 0000000080050033 cr4: 00000000000006e0
(XEN) [2019-10-30 22:07:46.840] cr3: 0000000428eb1000 cr2: ffff88805710cf60
(XEN) [2019-10-30 22:07:46.840] fsb: 00007f98c98d1bc0 gsb: ffff88807d4c0000 gss: 0000000000000000
(XEN) [2019-10-30 22:07:46.840] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) [2019-10-30 22:07:46.840] Xen code around <ffff82d080265748> (iommu_map.c#update_paging_mode+0x1f2/0x3eb):
(XEN) [2019-10-30 22:07:46.840] 3d 3b 7b 22 00 00 75 07 <0f> 0b e9 c2 01 00 00 48 8d 35 1a ce 13 00 48 8d
(XEN) [2019-10-30 22:07:46.840] Xen stack trace from rsp=ffff830523f7f808:
(XEN) [2019-10-30 22:07:46.840] ffff82e0036ad640 ffff82e0036ad640 ffff8301b56e8000 ffff8301b56e8000
(XEN) [2019-10-30 22:07:46.840] ffff8301b56e8148 00000000000feff8 ffff8301b56e8150 ffff830523f7f93c
(XEN) [2019-10-30 22:07:46.840] ffff830523f7f8c8 ffff82d080265ded 0000000380240580 00000000001a04a5
(XEN) [2019-10-30 22:07:46.840] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:46.840] 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:46.840] ffff8301b56e8000 00000000000feff8 00000000000feff8 00000000001a04a5
(XEN) [2019-10-30 22:07:46.840] ffff830523f7f928 ffff82d0802583b6 00000000000feff8 0000000000000001
(XEN) [2019-10-30 22:07:46.840] 00000003802405da 00000000001a04a5 ffff830523f7f93c 0000000000000003
(XEN) [2019-10-30 22:07:46.840] ffff8301b56e8000 00000000000feff8 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:46.840] ffff830523f7f960 ffff82d0802586fb 00000000b56fbc80 0000000000000003
(XEN) [2019-10-30 22:07:46.840] 0000000000000000 ffff8301b56fbc80 00000000000feff8 ffff830523f7f9f8
(XEN) [2019-10-30 22:07:46.840] ffff82d08034a4a6 000000008038a845 0000000000000000 ffff82004000bfc0
(XEN) [2019-10-30 22:07:46.840] ffff8301b56e8000 00000000001a04a5 0000000000000000 80000001b4b61367
(XEN) [2019-10-30 22:07:46.840] ffff82004005ff60 80000001b4b61367 0000000000000000 0000000000000000
(XEN) [2019-10-30 22:07:46.840] ffff82004000b000 0000000000000000 00000000001a04a5 00000000000feff8
(XEN) [2019-10-30 22:07:46.840] 0000000000000001 ffff8301b56fbc80 ffff830523f7fa50 ffff82d080342e13
(XEN) [2019-10-30 22:07:46.840] ffffffffffffffff 0000000000000007 ffff8301b56e8000 0000000000000023
(XEN) [2019-10-30 22:07:46.840] 00000000001a04a6 ffff8301b56fbc80 0000000000000000 00000000001a04a5
(XEN) [2019-10-30 22:07:46.840] 00000000000feff8 ffff830523f7fac8 ffff82d080343c52 0000000023f7fa78
(XEN) [2019-10-30 22:07:46.840] 0000000000000001 00000000001a04a5 00000000000feff8 ffff830523f7fa98
(XEN) [2019-10-30 22:07:46.840] Xen call trace:
(XEN) [2019-10-30 22:07:46.840] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
(XEN) [2019-10-30 22:07:46.840] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
(XEN) [2019-10-30 22:07:46.840] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
(XEN) [2019-10-30 22:07:46.840] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
(XEN) [2019-10-30 22:07:46.840] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
(XEN) [2019-10-30 22:07:46.840] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
(XEN) [2019-10-30 22:07:46.840] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
(XEN) [2019-10-30 22:07:46.840] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
(XEN) [2019-10-30 22:07:46.840] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
(XEN) [2019-10-30 22:07:46.840] [<ffff82d0802221e8>] F do_memory_op+0x695/0x1bf7
(XEN) [2019-10-30 22:07:46.840] [<ffff82d080383601>] F pv_hypercall+0x2ca/0x537
(XEN) [2019-10-30 22:07:46.840] [<ffff82d08038a432>] F lstar_enter+0x112/0x120
(XEN) [2019-10-30 22:07:46.840]
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: CPU
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: CPU
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: PIC
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: IOAPIC
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: LAPIC
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: LAPIC
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: PCI_IRQ
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: ISA_IRQ
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: PCI_LINK
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: PIT
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: RTC
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: HPET
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: PMTIMER
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: MTRR
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: MTRR
(XEN) [2019-10-30 22:07:46.840] HVM d15 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:07:46.840] HVM d15v0 save: CPU_MSR
(XEN) [2019-10-30 22:07:46.840] HVM d15v1 save: CPU_MSR
(XEN) [2019-10-30 22:07:46.841] HVM15 restore: CPU 0
(XEN) [2019-10-30 22:07:52.230] Dom9 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:07:53.971] memory_map:remove: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.975] memory_map:add: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.979] memory_map:remove: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.982] memory_map:add: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.984] memory_map:remove: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.987] memory_map:add: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.990] memory_map:remove: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.993] memory_map:add: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.995] memory_map:remove: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:53.998] memory_map:add: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:54.001] memory_map:remove: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:54.004] memory_map:add: dom9 gfn=f3050 mfn=fdef8 nr=4
(XEN) [2019-10-30 22:07:54.009] irq.c:374: Dom9 PCI link 0 changed 5 -> 0
(XEN) [2019-10-30 22:07:54.011] irq.c:374: Dom9 PCI link 1 changed 10 -> 0
(XEN) [2019-10-30 22:07:54.013] irq.c:374: Dom9 PCI link 2 changed 11 -> 0
(XEN) [2019-10-30 22:07:54.014] irq.c:374: Dom9 PCI link 3 changed 5 -> 0
(XEN) [2019-10-30 22:07:54.943] grant_table.c:1786:d9v1 Expanding d9 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:07:54.943] grant_table.c:1786:d9v1 Expanding d9 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:07:56.022] d15: bind: m_gsi=47 g_gsi=36 dev=00.00.5 intx=0
(XEN) [2019-10-30 22:07:56.029] AMD-Vi: Disable: device id = 0x900, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.029] AMD-Vi: Setup I/O page table: device id = 0x900, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.029] AMD-Vi: Re-assign 0000:09:00.0 from dom0 to dom15
(XEN) [2019-10-30 22:07:56.039] d15: bind: m_gsi=47 g_gsi=40 dev=00.00.6 intx=0
(XEN) [2019-10-30 22:07:56.048] AMD-Vi: Disable: device id = 0x901, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.048] AMD-Vi: Setup I/O page table: device id = 0x901, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.048] AMD-Vi: Re-assign 0000:09:00.1 from dom0 to dom15
(XEN) [2019-10-30 22:07:56.058] d15: bind: m_gsi=44 g_gsi=45 dev=00.00.7 intx=1
(XEN) [2019-10-30 22:07:56.071] AMD-Vi: Disable: device id = 0x903, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.071] AMD-Vi: Setup I/O page table: device id = 0x903, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.071] AMD-Vi: Re-assign 0000:09:00.3 from dom0 to dom15
(XEN) [2019-10-30 22:07:56.080] d15: bind: m_gsi=45 g_gsi=19 dev=00.01.0 intx=2
(XEN) [2019-10-30 22:07:56.096] AMD-Vi: Disable: device id = 0x905, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.096] AMD-Vi: Setup I/O page table: device id = 0x905, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.096] AMD-Vi: Re-assign 0000:09:00.5 from dom0 to dom15
(XEN) [2019-10-30 22:07:56.105] d15: bind: m_gsi=46 g_gsi=24 dev=00.01.1 intx=3
(XEN) [2019-10-30 22:07:56.126] AMD-Vi: Disable: device id = 0x906, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.126] AMD-Vi: Setup I/O page table: device id = 0x906, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.126] AMD-Vi: Re-assign 0000:09:00.6 from dom0 to dom15
(XEN) [2019-10-30 22:07:56.134] d15: bind: m_gsi=46 g_gsi=28 dev=00.01.2 intx=3
(XEN) [2019-10-30 22:07:56.158] AMD-Vi: Disable: device id = 0x907, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.158] AMD-Vi: Setup I/O page table: device id = 0x907, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.158] AMD-Vi: Re-assign 0000:09:00.7 from dom0 to dom15
(XEN) [2019-10-30 22:07:56.166] d15: bind: m_gsi=45 g_gsi=31 dev=00.01.3 intx=2
(XEN) [2019-10-30 22:07:56.197] AMD-Vi: Disable: device id = 0x904, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.197] AMD-Vi: Setup I/O page table: device id = 0x904, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.197] AMD-Vi: Re-assign 0000:09:00.4 from dom0 to dom15
(XEN) [2019-10-30 22:07:56.205] d15: bind: m_gsi=44 g_gsi=34 dev=00.01.4 intx=1
(XEN) [2019-10-30 22:07:56.240] AMD-Vi: Disable: device id = 0x902, domain = 0, paging mode = 3
(XEN) [2019-10-30 22:07:56.240] AMD-Vi: Setup I/O page table: device id = 0x902, type = 0x1, root table = 0x1a04a4000, domain = 15, paging mode = 3
(XEN) [2019-10-30 22:07:56.240] AMD-Vi: Re-assign 0000:09:00.2 from dom0 to dom15
(d15) [2019-10-30 22:07:56.275] HVM Loader
(d15) [2019-10-30 22:07:56.275] Detected Xen v4.13.0-rc
(d15) [2019-10-30 22:07:56.275] Xenbus rings @0xfeffc000, event channel 1
(d15) [2019-10-30 22:07:56.275] System requested SeaBIOS
(d15) [2019-10-30 22:07:56.275] CPU speed is 3200 MHz
(d15) [2019-10-30 22:07:56.275] Relocating guest memory for lowmem MMIO space disabled
(XEN) [2019-10-30 22:07:56.284] irq.c:374: Dom15 PCI link 0 changed 0 -> 5
(d15) [2019-10-30 22:07:56.284] PCI-ISA link 0 routed to IRQ5
(XEN) [2019-10-30 22:07:56.293] irq.c:374: Dom15 PCI link 1 changed 0 -> 10
(d15) [2019-10-30 22:07:56.293] PCI-ISA link 1 routed to IRQ10
(XEN) [2019-10-30 22:07:56.301] irq.c:374: Dom15 PCI link 2 changed 0 -> 11
(d15) [2019-10-30 22:07:56.301] PCI-ISA link 2 routed to IRQ11
(XEN) [2019-10-30 22:07:56.309] irq.c:374: Dom15 PCI link 3 changed 0 -> 5
(d15) [2019-10-30 22:07:56.309] PCI-ISA link 3 routed to IRQ5
(d15) [2019-10-30 22:07:56.516] pci dev 01:3 INTA->IRQ10
(d15) [2019-10-30 22:07:56.518] pci dev 02:0 INTA->IRQ11
(d15) [2019-10-30 22:07:56.522] pci dev 04:0 INTA->IRQ5
(d15) [2019-10-30 22:07:56.525] pci dev 05:0 INTA->IRQ10
(d15) [2019-10-30 22:07:56.527] pci dev 06:0 INTA->IRQ11
(d15) [2019-10-30 22:07:56.530] pci dev 07:0 INTB->IRQ5
(d15) [2019-10-30 22:07:56.532] pci dev 08:0 INTC->IRQ11
(d15) [2019-10-30 22:07:56.535] pci dev 09:0 INTD->IRQ5
(d15) [2019-10-30 22:07:56.537] pci dev 0a:0 INTD->IRQ10
(d15) [2019-10-30 22:07:56.540] pci dev 0b:0 INTC->IRQ10
(d15) [2019-10-30 22:07:56.542] pci dev 0c:0 INTB->IRQ10
(d15) [2019-10-30 22:07:56.553] RAM in high memory; setting high_mem resource base to 100000000
(d15) [2019-10-30 22:07:56.553] pci dev 03:0 bar 10 size 002000000: 0f0000008
(d15) [2019-10-30 22:07:56.553] pci dev 02:0 bar 14 size 001000000: 0f2000008
(d15) [2019-10-30 22:07:56.554] pci dev 04:0 bar 30 size 000040000: 0f3000000
(d15) [2019-10-30 22:07:56.555] pci dev 04:0 bar 10 size 000020000: 0f3040000
(d15) [2019-10-30 22:07:56.555] pci dev 03:0 bar 30 size 000010000: 0f3060000
(d15) [2019-10-30 22:07:56.555] pci dev 03:0 bar 14 size 000001000: 0f3070000
(d15) [2019-10-30 22:07:56.555] pci dev 05:0 bar 10 size 000001000: 0f3071000
(XEN) [2019-10-30 22:07:56.556] memory_map:add: dom15 gfn=f3071 mfn=fe4f8 nr=1
(d15) [2019-10-30 22:07:56.558] pci dev 06:0 bar 10 size 000001000: 0f3072000
(XEN) [2019-10-30 22:07:56.559] memory_map:add: dom15 gfn=f3072 mfn=fe4f9 nr=1
(d15) [2019-10-30 22:07:56.560] pci dev 07:0 bar 10 size 000001000: 0f3073000
(XEN) [2019-10-30 22:07:56.561] memory_map:add: dom15 gfn=f3073 mfn=fe4fb nr=1
(d15) [2019-10-30 22:07:56.563] pci dev 08:0 bar 10 size 000001000: 0f3074000
(XEN) [2019-10-30 22:07:56.563] memory_map:add: dom15 gfn=f3074 mfn=fe4fd nr=1
(d15) [2019-10-30 22:07:56.566] pci dev 09:0 bar 10 size 000001000: 0f3075000
(XEN) [2019-10-30 22:07:56.566] memory_map:add: dom15 gfn=f3075 mfn=fe4fe nr=1
(d15) [2019-10-30 22:07:56.569] pci dev 0a:0 bar 10 size 000001000: 0f3076000
(XEN) [2019-10-30 22:07:56.569] memory_map:add: dom15 gfn=f3076 mfn=fe4ff nr=1
(d15) [2019-10-30 22:07:56.571] pci dev 0b:0 bar 10 size 000001000: 0f3077000
(XEN) [2019-10-30 22:07:56.572] memory_map:add: dom15 gfn=f3077 mfn=fe4fc nr=1
(d15) [2019-10-30 22:07:56.574] pci dev 0c:0 bar 10 size 000001000: 0f3078000
(XEN) [2019-10-30 22:07:56.575] memory_map:add: dom15 gfn=f3078 mfn=fe4fa nr=1
(d15) [2019-10-30 22:07:56.577] pci dev 02:0 bar 10 size 000000100: 00000c001
(d15) [2019-10-30 22:07:56.578] pci dev 04:0 bar 14 size 000000040: 00000c101
(d15) [2019-10-30 22:07:56.578] pci dev 01:1 bar 20 size 000000010: 00000c141
(d15) [2019-10-30 22:07:56.579] Multiprocessor initialisation:
(d15) [2019-10-30 22:07:56.581] - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d15) [2019-10-30 22:07:56.582] - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done.
(d15) [2019-10-30 22:07:56.583] Testing HVM environment:
(d15) [2019-10-30 22:07:56.583] Using scratch memory at 400000
(d15) [2019-10-30 22:07:56.595] - REP INSB across page boundaries ... passed
(d15) [2019-10-30 22:07:56.609] - REP INSW across page boundaries ... passed
(d15) [2019-10-30 22:07:56.621] - GS base MSRs and SWAPGS ... passed
(d15) [2019-10-30 22:07:56.621] Passed 3 of 3 tests
(d15) [2019-10-30 22:07:56.621] Writing SMBIOS tables ...
(d15) [2019-10-30 22:07:56.623] Loading SeaBIOS ...
(d15) [2019-10-30 22:07:56.623] Creating MP tables ...
(d15) [2019-10-30 22:07:56.623] Loading ACPI ...
(d15) [2019-10-30 22:07:56.624] vm86 TSS at fc00a980
(d15) [2019-10-30 22:07:56.624] BIOS map:
(d15) [2019-10-30 22:07:56.624] 10000-100e3: Scratch space
(d15) [2019-10-30 22:07:56.624] c0000-fffff: Main BIOS
(d15) [2019-10-30 22:07:56.624] E820 table:
(d15) [2019-10-30 22:07:56.624] [00]: 00000000:00000000 - 00000000:000a0000: RAM
(d15) [2019-10-30 22:07:56.624] HOLE: 00000000:000a0000 - 00000000:000c0000
(d15) [2019-10-30 22:07:56.624] [01]: 00000000:000c0000 - 00000000:00100000: RESERVED
(d15) [2019-10-30 22:07:56.624] [02]: 00000000:00100000 - 00000000:3f800000: RAM
(d15) [2019-10-30 22:07:56.624] HOLE: 00000000:3f800000 - 00000000:fc000000
(d15) [2019-10-30 22:07:56.624] [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(d15) [2019-10-30 22:07:56.624] [04]: 00000001:00000000 - 00000001:00000000: RAM
(d15) [2019-10-30 22:07:56.624] Invoking SeaBIOS ...
(d15) [2019-10-30 22:07:56.625] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d15) [2019-10-30 22:07:56.625] BUILD: gcc: (Debian 8.3.0-6) 8.3.0 binutils: (GNU Binutils for Debian) 2.31.1
(d15) [2019-10-30 22:07:56.625]
(d15) [2019-10-30 22:07:56.625] Found Xen hypervisor signature at 40000000
(d15) [2019-10-30 22:07:56.625] Running on QEMU (i440fx)
(d15) [2019-10-30 22:07:56.625] xen: copy e820...
(d15) [2019-10-30 22:07:56.625] Relocating init from 0x000d8920 to 0x3f7ac480 (size 80608)
(d15) [2019-10-30 22:07:56.625] Found QEMU fw_cfg
(d15) [2019-10-30 22:07:56.626] RamSizeOver4G: 0x0000000000000000 [cmos]
(d15) [2019-10-30 22:07:56.627] boot order:
(d15) [2019-10-30 22:07:56.627] 1: /rom@genroms/linuxboot.bin
(d15) [2019-10-30 22:07:56.632] Found 15 PCI devices (max PCI bus is 00)
(d15) [2019-10-30 22:07:56.632] Allocated Xen hypercall page at 3f7ff000
(d15) [2019-10-30 22:07:56.632] Detected Xen v4.13.0-rc
(d15) [2019-10-30 22:07:56.632] xen: copy BIOS tables...
(d15) [2019-10-30 22:07:56.632] Copying SMBIOS entry point from 0x00010020 to 0x000f5be0
(d15) [2019-10-30 22:07:56.632] Copying MPTABLE from 0xfc001180/fc001190 to 0x000f5ae0
(d15) [2019-10-30 22:07:56.632] Copying PIR from 0x00010040 to 0x000f5a60
(d15) [2019-10-30 22:07:56.632] Copying ACPI RSDP from 0x000100c0 to 0x000f5a30
(d15) [2019-10-30 22:07:56.632] Using pmtimer, ioport 0xb008
(d15) [2019-10-30 22:07:56.632] Scan for VGA option rom
(d15) [2019-10-30 22:07:56.642] Running option rom at c000:0003
(XEN) [2019-10-30 22:07:56.643] stdvga.c:173:d15v0 entering stdvga mode
(d15) [2019-10-30 22:07:56.654] pmm call arg1=0
(d15) [2019-10-30 22:07:56.654] Turning on vga text mode console
(d15) [2019-10-30 22:07:56.700] SeaBIOS (version rel-1.12.1-0-ga5cab58-Xen)
(d15) [2019-10-30 22:07:56.705] Machine UUID 4e95c3e4-a412-4048-82f1-97697601868a
(d15) [2019-10-30 22:07:56.706] EHCI init on dev 00:06.0 (regs=0xf3072020)
(d15) [2019-10-30 22:07:56.706] EHCI init on dev 00:07.0 (regs=0xf3073020)
(d15) [2019-10-30 22:07:56.706] EHCI init on dev 00:08.0 (regs=0xf3074020)
(d15) [2019-10-30 22:07:56.707] EHCI init on dev 00:0a.0 (regs=0xf3076020)
(d15) [2019-10-30 22:07:56.707] OHCI init on dev 00:05.0 (regs=0xf3071000)
(d15) [2019-10-30 22:07:56.707] OHCI init on dev 00:09.0 (regs=0xf3075000)
(d15) [2019-10-30 22:07:56.707] OHCI init on dev 00:0b.0 (regs=0xf3077000)
(d15) [2019-10-30 22:07:56.708] OHCI init on dev 00:0c.0 (regs=0xf3078000)
(d15) [2019-10-30 22:07:56.709] ATA controller 1 at 1f0/3f4/c140 (irq 14 dev 9)
(d15) [2019-10-30 22:07:56.709] ATA controller 2 at 170/374/c148 (irq 15 dev 9)
(d15) [2019-10-30 22:07:56.710] Found 0 lpt ports
(d15) [2019-10-30 22:07:56.710] Found 1 serial ports
(d15) [2019-10-30 22:07:56.711] PS2 keyboard initialized
(d15) [2019-10-30 22:07:56.712] ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (10240 MiBytes)
(d15) [2019-10-30 22:07:56.712] Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(d15) [2019-10-30 22:07:56.789] ehci_wait_td error - status=80248
(d15) [2019-10-30 22:07:56.789] ehci_wait_td error - status=80248
(d15) [2019-10-30 22:08:01.863] WARNING - Timeout at ohci_waittick:136!
(d15) [2019-10-30 22:08:01.863] WARNING - Timeout at ohci_waittick:136!
(d15) [2019-10-30 22:08:01.863] WARNING - Timeout at ohci_waittick:136!
(d15) [2019-10-30 22:08:01.864] WARNING - Timeout at ohci_waittick:136!
(d15) [2019-10-30 22:08:01.864] All threads complete.
(d15) [2019-10-30 22:08:01.864] Scan for option roms
(d15) [2019-10-30 22:08:01.886] Running option rom at c980:0003
(d15) [2019-10-30 22:08:01.894] pmm call arg1=1
(d15) [2019-10-30 22:08:01.894] pmm call arg1=0
(d15) [2019-10-30 22:08:01.895] pmm call arg1=1
(d15) [2019-10-30 22:08:01.895] pmm call arg1=0
(d15) [2019-10-30 22:08:01.914] Running option rom at ca80:0003
(d15) [2019-10-30 22:08:01.914] Searching bootorder for: /pci@i0cf8/*@4
(d15) [2019-10-30 22:08:01.914] Searching bootorder for: /rom@genroms/linuxboot.bin
(d15) [2019-10-30 22:08:01.914] Searching bootorder for: HALT
(d15) [2019-10-30 22:08:01.914] drive 0x000f59c0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=20971520
(d15) [2019-10-30 22:08:01.915] Space available for UMB: cb000-eb800, f5400-f59c0
(d15) [2019-10-30 22:08:01.915] Returned 258048 bytes of ZoneHigh
(d15) [2019-10-30 22:08:01.915] e820 map has 6 items:
(d15) [2019-10-30 22:08:01.915] 0: 0000000000000000 - 000000000009fc00 = 1 RAM
(d15) [2019-10-30 22:08:01.915] 1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(d15) [2019-10-30 22:08:01.915] 2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(d15) [2019-10-30 22:08:01.915] 3: 0000000000100000 - 000000003f7ff000 = 1 RAM
(d15) [2019-10-30 22:08:01.915] 4: 000000003f7ff000 - 000000003f800000 = 2 RESERVED
(d15) [2019-10-30 22:08:01.915] 5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(d15) [2019-10-30 22:08:01.916] enter handle_19:
(d15) [2019-10-30 22:08:01.916] NULL
(d15) [2019-10-30 22:08:01.920] Booting from ROM...
(d15) [2019-10-30 22:08:01.920] Booting from ca80:003c
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: CPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: CPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: CPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: CPU
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: PIC
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: IOAPIC
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: LAPIC
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: LAPIC
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: LAPIC
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: LAPIC
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: LAPIC_REGS
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: LAPIC_REGS
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: LAPIC_REGS
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: LAPIC_REGS
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: PCI_IRQ
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: ISA_IRQ
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: PCI_LINK
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: PIT
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: RTC
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: HPET
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: PMTIMER
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: MTRR
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: MTRR
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: MTRR
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: MTRR
(XEN) [2019-10-30 22:08:02.120] HVM d16 save: VIRIDIAN_DOMAIN
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: CPU_XSAVE
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: CPU_XSAVE
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: CPU_XSAVE
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: CPU_XSAVE
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: VIRIDIAN_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: VMCE_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: VMCE_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: VMCE_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: VMCE_VCPU
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: TSC_ADJUST
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: TSC_ADJUST
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: TSC_ADJUST
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: TSC_ADJUST
(XEN) [2019-10-30 22:08:02.120] HVM d16v0 save: CPU_MSR
(XEN) [2019-10-30 22:08:02.120] HVM d16v1 save: CPU_MSR
(XEN) [2019-10-30 22:08:02.120] HVM d16v2 save: CPU_MSR
(XEN) [2019-10-30 22:08:02.120] HVM d16v3 save: CPU_MSR
(XEN) [2019-10-30 22:08:02.121] HVM16 restore: MTRR 0
(XEN) [2019-10-30 22:08:02.121] HVM16 restore: MTRR 1
(XEN) [2019-10-30 22:08:02.121] HVM16 restore: MTRR 2
(XEN) [2019-10-30 22:08:02.121] HVM16 restore: MTRR 3
(XEN) [2019-10-30 22:08:02.121] HVM16 restore: CPU 0
(XEN) [2019-10-30 22:08:02.930] Dom16 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:08:04.182] grant_table.c:1786:d16v2 Expanding d16 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:08:04.182] grant_table.c:1786:d16v2 Expanding d16 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:08:04.182] grant_table.c:1786:d16v2 Expanding d16 grant table from 3 to 4 frames
(XEN) [2019-10-30 22:08:04.182] grant_table.c:1786:d16v2 Expanding d16 grant table from 4 to 5 frames
(XEN) [2019-10-30 22:08:26.072] Dom14 callback via changed to Direct Vector 0xf3
(XEN) [2019-10-30 22:08:28.641] memory_map:remove: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.644] memory_map:add: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.655] memory_map:remove: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.658] memory_map:add: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.661] memory_map:remove: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.663] memory_map:add: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.666] memory_map:remove: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.669] memory_map:add: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.671] memory_map:remove: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.674] memory_map:add: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.677] memory_map:remove: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.679] memory_map:add: dom14 gfn=f3070 mfn=fe3fe nr=1
(XEN) [2019-10-30 22:08:28.697] irq.c:374: Dom14 PCI link 0 changed 5 -> 0
(XEN) [2019-10-30 22:08:28.704] irq.c:374: Dom14 PCI link 1 changed 10 -> 0
(XEN) [2019-10-30 22:08:28.711] irq.c:374: Dom14 PCI link 2 changed 11 -> 0
(XEN) [2019-10-30 22:08:28.718] irq.c:374: Dom14 PCI link 3 changed 5 -> 0
(XEN) [2019-10-30 22:08:30.573] grant_table.c:1786:d14v1 Expanding d14 grant table from 1 to 2 frames
(XEN) [2019-10-30 22:08:30.574] grant_table.c:1786:d14v1 Expanding d14 grant table from 2 to 3 frames
(XEN) [2019-10-30 22:08:30.574] grant_table.c:1786:d14v1 Expanding d14 grant table from 3 to 4 frames
(XEN) [2019-10-30 22:08:30.574] grant_table.c:1786:d14v1 Expanding d14 grant table from 4 to 5 frames
(XEN) [2019-10-30 22:08:30.700] AMD-Vi: INVALID_DEV_REQUEST 00000800 8a000000 f8002040 000000fd
(XEN) [2019-10-30 22:08:38.886] grant_table.c:1786:d14v0 Expanding d14 grant table from 5 to 6 frames
(XEN) [2019-10-30 22:08:43.181] grant_table.c:1786:d14v0 Expanding d14 grant table from 6 to 7 frames
(XEN) [2019-10-30 22:08:45.357] Dom15 callback via changed to Direct Vector 0xf3
[-- Attachment #3: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-31 8:35 ` Sander Eikelenboom
@ 2019-10-31 9:18 ` Jan Beulich
2019-10-31 9:36 ` Sander Eikelenboom
0 siblings, 1 reply; 15+ messages in thread
From: Jan Beulich @ 2019-10-31 9:18 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, xen-devel
On 31.10.2019 09:35, Sander Eikelenboom wrote:
> Platform is perhaps what specific (older AMD 890FX chipset) and I need the bios workaround:
> ivrs_ioapic[6]=00:14.0 iommu=on.
Shouldn't matter here.
> On the other hand, this has ran like this for quite some time.
>
> I have 3 guests (HVM) for which i use PCI passthrough and
> for each of those 3 guests I get this message *once* on start of the guest.
> One guest has a soundcard passed through,
> One guest has a USB2 card passed through,
> One guest has a USB3 card passed through.
>
> Another observation is that both the soundcard and USB2 card
> still seem to function despite the message.
Reality is - this message is benign as long as you don't do PCI
hot (un)plug.
> The USB3 controller goes haywire though (a lot of driver messages in the guest during init).
As a consequence I don't think there's a connection between this
and the observed message.
> I could try to bisect, but that would be somewhere next week before I can get to that.
>
> At present I run with a tree with as latest commit ee7170822f1fc209f33feb47b268bab35541351d,
> which is stable for me. This predates some of the IOMMU changes and Anthony's QMP work that had
> some issues, but that would be the last known real good point for me to start a bisect from.
I.e. at that point you didn't observe this message, yet?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-31 9:18 ` Jan Beulich
@ 2019-10-31 9:36 ` Sander Eikelenboom
0 siblings, 0 replies; 15+ messages in thread
From: Sander Eikelenboom @ 2019-10-31 9:36 UTC (permalink / raw)
To: Jan Beulich; +Cc: Juergen Gross, Andrew Cooper, xen-devel
On 31/10/2019 10:18, Jan Beulich wrote:
> On 31.10.2019 09:35, Sander Eikelenboom wrote:
>> Platform is perhaps what specific (older AMD 890FX chipset) and I need the bios workaround:
>> ivrs_ioapic[6]=00:14.0 iommu=on.
>
> Shouldn't matter here.
>
>> On the other hand, this has ran like this for quite some time.
>>
>> I have 3 guests (HVM) for which i use PCI passthrough and
>> for each of those 3 guests I get this message *once* on start of the guest.
>> One guest has a soundcard passed through,
>> One guest has a USB2 card passed through,
>> One guest has a USB3 card passed through.
>>
>> Another observation is that both the soundcard and USB2 card
>> still seem to function despite the message.
>
> Reality is - this message is benign as long as you don't do PCI
> hot (un)plug.
I don't use any of:
pci-attach
pci-detach
pci-list
pci-assignable-add
pci-assignable-remove
pci-assignable-list
Only shutting down and (re)starting VMs with the devices specified in
the vm cfg file.
>> The USB3 controller goes haywire though (a lot of driver messages in the guest during init).
>
> As a consequence I don't think there's a connection between this
> and the observed message.
Ok, although it functions fine when (with same kernel etc. reverting to
the commit I referenced to below), if so, that would be another issue then.
CC'ed Juergen as release manager so he is aware.
>> I could try to bisect, but that would be somewhere next week before I can get to that.
>>
>> At present I run with a tree with as latest commit ee7170822f1fc209f33feb47b268bab35541351d,
>> which is stable for me. This predates some of the IOMMU changes and Anthony's QMP work that had
>> some issues, but that would be the last known real good point for me to start a bisect from.
>
> I.e. at that point you didn't observe this message, yet?
With ee7170822f1fc209f33feb47b268bab35541351d, nor this message, nor the
"INVALID_DEV_REQUEST", even with longer uptimes.
--
Sander
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-30 22:21 ` Sander Eikelenboom
2019-10-31 7:31 ` Jan Beulich
@ 2019-10-31 10:15 ` Jan Beulich
2019-10-31 20:48 ` Sander Eikelenboom
1 sibling, 1 reply; 15+ messages in thread
From: Jan Beulich @ 2019-10-31 10:15 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, Paul Durrant, xen-devel
On 30.10.2019 23:21, Sander Eikelenboom wrote:
> Call trace seems to be the same in all cases.
>
> --
> Sander
>
>
> (XEN) [2019-10-30 22:07:05.748] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
> (XEN) [2019-10-30 22:07:05.748] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
> (XEN) [2019-10-30 22:07:05.748] CPU: 1
> (XEN) [2019-10-30 22:07:05.748] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
> (XEN) [2019-10-30 22:07:05.748] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v2)
I didn't pay attention to this when writing my earlier reply: The
likely culprit looks to be f89f555827 ("remove late (on-demand)
construction of IOMMU page tables"). Prior to this I assume IOMMU
page tables got constructed only after ...
> (XEN) [2019-10-30 22:07:05.748] Xen call trace:
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
... Dom0 had populated the new guest's physmap.
Anyway, as odd as it may seem I guess there's little choice
besides making populate_physmap() (and likely a few others)
acquire the lock.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-31 10:15 ` Jan Beulich
@ 2019-10-31 20:48 ` Sander Eikelenboom
2019-11-11 15:35 ` Jan Beulich
2019-11-11 16:07 ` Jan Beulich
0 siblings, 2 replies; 15+ messages in thread
From: Sander Eikelenboom @ 2019-10-31 20:48 UTC (permalink / raw)
To: Jan Beulich; +Cc: Andrew Cooper, Paul Durrant, xen-devel
On 31/10/2019 11:15, Jan Beulich wrote:
> On 30.10.2019 23:21, Sander Eikelenboom wrote:
>> Call trace seems to be the same in all cases.
>>
>> --
>> Sander
>>
>>
>> (XEN) [2019-10-30 22:07:05.748] AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
>> (XEN) [2019-10-30 22:07:05.748] ----[ Xen-4.13.0-rc x86_64 debug=y Not tainted ]----
>> (XEN) [2019-10-30 22:07:05.748] CPU: 1
>> (XEN) [2019-10-30 22:07:05.748] RIP: e008:[<ffff82d080265748>] iommu_map.c#update_paging_mode+0x1f2/0x3eb
>> (XEN) [2019-10-30 22:07:05.748] RFLAGS: 0000000000010286 CONTEXT: hypervisor (d0v2)
>
> I didn't pay attention to this when writing my earlier reply: The
> likely culprit looks to be f89f555827 ("remove late (on-demand)
> construction of IOMMU page tables"). Prior to this I assume IOMMU
> page tables got constructed only after ...
OK, I tested f89f555827 and f89f555827~1, my observations:
with f89f555827~1:
- I'm NOT seeing the aquiring pcidevs_lock message
- the usb3 controller is also working.
with f89f555827:
- I'm now seeing the aquiring pcidevs_lock messages.
- but I'm NOT seeing them *once* per booting guest, but multiple times.
- the usb3 controller is still working.
with staging:
- Seeing the aquiring pcidevs_lock messages, but only *once* per guest boot.
- the usb3 controller goes haywire in the guest.
So you seem to be right about both things:
- f89f555827 is the culprit for the aquiring pcidevs_lock messages.
Although I get less of them with current staging, so some other later patch must have had some influence
in reducing the amount.
- The usb3 controller malfunctioning seems indeed to be a separate issue (which seems unfortunate,
because a bisect seems to become even nastier with all the intertwined pci-passthrough issues).
Perhaps this one is then related to the only *once* occuring message:
(XEN) [2019-10-31 20:39:30.746] AMD-Vi: INVALID_DEV_REQUEST 00000800 8a000000 f8000840 000000fd
While in the guest it is endlessly repeating:
[ 231.385566] xhci_hcd 0000:00:05.0: Max number of devices this xHCI host supports is 32.
[ 231.407351] usb usb1-port2: couldn't allocate usb_device
Hopefully this also gives you a hunch as to which commits to look at.
--
Sander
>> (XEN) [2019-10-30 22:07:05.748] Xen call trace:
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265748>] R iommu_map.c#update_paging_mode+0x1f2/0x3eb
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080265ded>] F amd_iommu_map_page+0x72/0x1c2
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802583b6>] F iommu_map+0x98/0x17e
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802586fb>] F iommu_legacy_map+0x28/0x73
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d08034a4a6>] F p2m-pt.c#p2m_pt_set_entry+0x4d3/0x844
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080342e13>] F p2m_set_entry+0x91/0x128
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343c52>] F guest_physmap_add_entry+0x39f/0x5a3
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d080343f85>] F guest_physmap_add_page+0x12f/0x138
>> (XEN) [2019-10-30 22:07:05.748] [<ffff82d0802201ee>] F memory.c#populate_physmap+0x2e3/0x505
>
> ... Dom0 had populated the new guest's physmap.
>
> Anyway, as odd as it may seem I guess there's little choice
> besides making populate_physmap() (and likely a few others)
> acquire the lock.
>
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-31 20:48 ` Sander Eikelenboom
@ 2019-11-11 15:35 ` Jan Beulich
2019-11-11 21:38 ` Sander Eikelenboom
2019-11-11 16:07 ` Jan Beulich
1 sibling, 1 reply; 15+ messages in thread
From: Jan Beulich @ 2019-11-11 15:35 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, Paul Durrant, xen-devel
On 31.10.2019 21:48, Sander Eikelenboom wrote:
> - The usb3 controller malfunctioning seems indeed to be a separate issue (which seems unfortunate,
> because a bisect seems to become even nastier with all the intertwined pci-passthrough issues).
>
> Perhaps this one is then related to the only *once* occuring message:
> (XEN) [2019-10-31 20:39:30.746] AMD-Vi: INVALID_DEV_REQUEST 00000800 8a000000 f8000840 000000fd
>
> While in the guest it is endlessly repeating:
> [ 231.385566] xhci_hcd 0000:00:05.0: Max number of devices this xHCI host supports is 32.
> [ 231.407351] usb usb1-port2: couldn't allocate usb_device
I'm uncertain whether there's a correlation: The device the Xen
message is about is 08:00.0; please let us know what kind of device
that is (the hypervisor log alone don't allow me to guess).
The specific type is described as "Posted write to the Interrupt/EOI
range from an I/O device that has IntCtl=00b in the device’s DTE."
This would make me guess 1b00c16bdf ("AMD/IOMMU: pre-fill all DTEs
right after table allocation") is the culprit here, and I may need
to hand you a debugging patch to gain some insight. But let me first
take a look at sufficiently verbose lspci output from that system.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-10-31 20:48 ` Sander Eikelenboom
2019-11-11 15:35 ` Jan Beulich
@ 2019-11-11 16:07 ` Jan Beulich
1 sibling, 0 replies; 15+ messages in thread
From: Jan Beulich @ 2019-11-11 16:07 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, Paul Durrant, xen-devel
On 31.10.2019 21:48, Sander Eikelenboom wrote:
> While in the guest it is endlessly repeating:
> [ 231.385566] xhci_hcd 0000:00:05.0: Max number of devices this xHCI host supports is 32.
> [ 231.407351] usb usb1-port2: couldn't allocate usb_device
For this one, could you try "pci=nomsi" on the Linux kernel command
line?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-11-11 15:35 ` Jan Beulich
@ 2019-11-11 21:38 ` Sander Eikelenboom
2019-11-12 11:05 ` Jan Beulich
0 siblings, 1 reply; 15+ messages in thread
From: Sander Eikelenboom @ 2019-11-11 21:38 UTC (permalink / raw)
To: Jan Beulich; +Cc: Andrew Cooper, Paul Durrant, xen-devel
On 11/11/2019 16:35, Jan Beulich wrote:
> On 31.10.2019 21:48, Sander Eikelenboom wrote:
>> - The usb3 controller malfunctioning seems indeed to be a separate issue (which seems unfortunate,
>> because a bisect seems to become even nastier with all the intertwined pci-passthrough issues).
>>
>> Perhaps this one is then related to the only *once* occuring message:
>> (XEN) [2019-10-31 20:39:30.746] AMD-Vi: INVALID_DEV_REQUEST 00000800 8a000000 f8000840 000000fd
>>
>> While in the guest it is endlessly repeating:
>> [ 231.385566] xhci_hcd 0000:00:05.0: Max number of devices this xHCI host supports is 32.
>> [ 231.407351] usb usb1-port2: couldn't allocate usb_device
>
> I'm uncertain whether there's a correlation: The device the Xen
> message is about is 08:00.0; please let us know what kind of device
> that is (the hypervisor log alone don't allow me to guess).
>
> The specific type is described as "Posted write to the Interrupt/EOI
> range from an I/O device that has IntCtl=00b in the device’s DTE."
> This would make me guess 1b00c16bdf ("AMD/IOMMU: pre-fill all DTEs
> right after table allocation") is the culprit here, and I may need
> to hand you a debugging patch to gain some insight. But let me first
> take a look at sufficiently verbose lspci output from that system.
>
> Jan
>
Hi Jan,
When supplying "pci=nomsi" to the guest kernel, the device works fine,
and I don't get the "INVALID_DEV_REQUEST".
After reverting 1b00c16bdf, the device works fine
and I don't get the INVALID_DEV_REQUEST,
Below is the output of lspci -vvvknn from dom0 for 08:00.0:
- just after boot (device owned by pciback / dom0, not active yet)
- after the guests have started (owned by guest with a working device)
So it is enabling MSI-X interrupts, which is indeed different from the other devices I pass through which
seem to use legacy interrupts.
This also shows in the guest with a working device in /proc/interrupts:
98: 17846 0 0 0 xen-pirq -msi-x xhci_hcd
99: 0 0 0 0 xen-pirq -msi-x xhci_hcd
100: 0 0 0 0 xen-pirq -msi-x xhci_hcd
101: 0 0 0 0 xen-pirq -msi-x xhci_hcd
102: 0 0 0 0 xen-pirq -msi-x xhci_hcd
I forgot to take a snapshot of /proc/interrupts in the guest in the malfunctioning state.
--
Sander
just after boot (device owned by pciback / dom0, not active yet):
08:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 03) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard [1043:8413]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 37
NUMA node: 0
Region 0: Memory at fe3fe000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [90] MSI-X: Enable- Count=8 Masked-
Vector table: BAR=0 offset=00001000
PBA: BAR=0 offset=00001080
Capabilities: [a0] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 unlimited
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140 v1] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff
Capabilities: [150 v1] Latency Tolerance Reporting
Max snoop latency: 0ns
Max no snoop latency: 0ns
Kernel driver in use: pciback
after the guests have started (with a working device):
08:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 03) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard [1043:8413]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 37
NUMA node: 0
Region 0: Memory at fe3fe000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [90] MSI-X: Enable+ Count=8 Masked-
Vector table: BAR=0 offset=00001000
PBA: BAR=0 offset=00001080
Capabilities: [a0] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 unlimited
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140 v1] Device Serial Number ff-ff-ff-ff-ff-ff-ff-ff
Capabilities: [150 v1] Latency Tolerance Reporting
Max snoop latency: 0ns
Max no snoop latency: 0ns
Kernel driver in use: pciback
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-11-11 21:38 ` Sander Eikelenboom
@ 2019-11-12 11:05 ` Jan Beulich
2019-11-12 19:31 ` Sander Eikelenboom
0 siblings, 1 reply; 15+ messages in thread
From: Jan Beulich @ 2019-11-12 11:05 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Andrew Cooper, Paul Durrant, xen-devel
On 11.11.2019 22:38, Sander Eikelenboom wrote:
> When supplying "pci=nomsi" to the guest kernel, the device works fine,
> and I don't get the "INVALID_DEV_REQUEST".
>
> After reverting 1b00c16bdf, the device works fine
> and I don't get the INVALID_DEV_REQUEST,
Could you give the patch below a try? That commit took care of only
securing ourselves, but not of relaxing things again when a device
gets handed to a guest for actual use.
Jan
AMD/IOMMU: restore DTE fields in amd_iommu_setup_domain_device()
Commit 1b00c16bdf ("AMD/IOMMU: pre-fill all DTEs right after table
allocation") moved ourselves into a more secure default state, but
didn't take sufficient care to also undo the effects when handing a
previously disabled device back to a(nother) domain. Put the fields
that may have been changed elsewhere back to their intended values
(some fields amd_iommu_disable_domain_device() touches don't
currently get written anywhere else, and hence don't need modifying
here).
Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- unstable.orig/xen/drivers/passthrough/amd/pci_amd_iommu.c
+++ unstable/xen/drivers/passthrough/amd/pci_amd_iommu.c
@@ -114,11 +114,21 @@ static void amd_iommu_setup_domain_devic
if ( !dte->v || !dte->tv )
{
+ const struct ivrs_mappings *ivrs_dev;
+
/* bind DTE to domain page-tables */
amd_iommu_set_root_page_table(
dte, page_to_maddr(hd->arch.root_table), domain->domain_id,
hd->arch.paging_mode, valid);
+ /* Undo what amd_iommu_disable_domain_device() may have done. */
+ ivrs_dev = &get_ivrs_mappings(iommu->seg)[req_id];
+ if ( dte->it_root )
+ dte->int_ctl = IOMMU_DEV_TABLE_INT_CONTROL_TRANSLATED;
+ dte->iv = iommu_intremap;
+ dte->ex = ivrs_dev->dte_allow_exclusion;
+ dte->sys_mgt = MASK_EXTR(ivrs_dev->device_flags, ACPI_IVHD_SYSTEM_MGMT);
+
if ( pci_ats_device(iommu->seg, bus, pdev->devfn) &&
iommu_has_cap(iommu, PCI_CAP_IOTLB_SHIFT) )
dte->i = ats_enabled;
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock.
2019-11-12 11:05 ` Jan Beulich
@ 2019-11-12 19:31 ` Sander Eikelenboom
0 siblings, 0 replies; 15+ messages in thread
From: Sander Eikelenboom @ 2019-11-12 19:31 UTC (permalink / raw)
To: Jan Beulich; +Cc: Juergen Gross, Andrew Cooper, Paul Durrant, xen-devel
On 12/11/2019 12:05, Jan Beulich wrote:
> On 11.11.2019 22:38, Sander Eikelenboom wrote:
>> When supplying "pci=nomsi" to the guest kernel, the device works fine,
>> and I don't get the "INVALID_DEV_REQUEST".
>>
>> After reverting 1b00c16bdf, the device works fine
>> and I don't get the INVALID_DEV_REQUEST,
>
> Could you give the patch below a try? That commit took care of only
> securing ourselves, but not of relaxing things again when a device
> gets handed to a guest for actual use.
>
> Jan
Hi Jan,
CC'ed Juergen, as he seems to be dropped off the CC-list at some time.
Just tested this patch:
the device works fine and I don't get the INVALID_DEV_REQUEST.
This was the last remaining issue around pci passthrough I encountered,
with all patches applied (yours and Anthony's) pci passthrough for me
seems to work again as I was used to.
Thanks again for fixing the issues and providing the right educated guesses!
--
Sander
> AMD/IOMMU: restore DTE fields in amd_iommu_setup_domain_device()
>
> Commit 1b00c16bdf ("AMD/IOMMU: pre-fill all DTEs right after table
> allocation") moved ourselves into a more secure default state, but
> didn't take sufficient care to also undo the effects when handing a
> previously disabled device back to a(nother) domain. Put the fields
> that may have been changed elsewhere back to their intended values
> (some fields amd_iommu_disable_domain_device() touches don't
> currently get written anywhere else, and hence don't need modifying
> here).
>
> Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- unstable.orig/xen/drivers/passthrough/amd/pci_amd_iommu.c
> +++ unstable/xen/drivers/passthrough/amd/pci_amd_iommu.c
> @@ -114,11 +114,21 @@ static void amd_iommu_setup_domain_devic
>
> if ( !dte->v || !dte->tv )
> {
> + const struct ivrs_mappings *ivrs_dev;
> +
> /* bind DTE to domain page-tables */
> amd_iommu_set_root_page_table(
> dte, page_to_maddr(hd->arch.root_table), domain->domain_id,
> hd->arch.paging_mode, valid);
>
> + /* Undo what amd_iommu_disable_domain_device() may have done. */
> + ivrs_dev = &get_ivrs_mappings(iommu->seg)[req_id];
> + if ( dte->it_root )
> + dte->int_ctl = IOMMU_DEV_TABLE_INT_CONTROL_TRANSLATED;
> + dte->iv = iommu_intremap;
> + dte->ex = ivrs_dev->dte_allow_exclusion;
> + dte->sys_mgt = MASK_EXTR(ivrs_dev->device_flags, ACPI_IVHD_SYSTEM_MGMT);
> +
> if ( pci_ats_device(iommu->seg, bus, pdev->devfn) &&
> iommu_has_cap(iommu, PCI_CAP_IOTLB_SHIFT) )
> dte->i = ats_enabled;
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2019-11-12 19:31 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-28 10:32 [Xen-devel] Xen-unstable: AMD-Vi: update_paging_mode Try to access pdev_list without aquiring pcidevs_lock Sander Eikelenboom
2019-10-28 10:38 ` Jan Beulich
2019-10-30 15:48 ` Jan Beulich
2019-10-30 22:21 ` Sander Eikelenboom
2019-10-31 7:31 ` Jan Beulich
2019-10-31 8:35 ` Sander Eikelenboom
2019-10-31 9:18 ` Jan Beulich
2019-10-31 9:36 ` Sander Eikelenboom
2019-10-31 10:15 ` Jan Beulich
2019-10-31 20:48 ` Sander Eikelenboom
2019-11-11 15:35 ` Jan Beulich
2019-11-11 21:38 ` Sander Eikelenboom
2019-11-12 11:05 ` Jan Beulich
2019-11-12 19:31 ` Sander Eikelenboom
2019-11-11 16:07 ` Jan Beulich
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.