* Xen-unstable: Bisected Host boot failure on AMD Phenom
@ 2017-03-02 14:42 Sander Eikelenboom
2017-03-02 14:55 ` Andrew Cooper
0 siblings, 1 reply; 14+ messages in thread
From: Sander Eikelenboom @ 2017-03-02 14:42 UTC (permalink / raw)
To: Andrew Cooper; +Cc: Jan Beulich, xen-devel
Hi Andrew / Jan,
While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
Bisection has turned up:
5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Fri Feb 17 17:10:50 2017 +0000
x86/cpuid: Handle leaf 0x1 in guest_cpuid()
Hardware is a AMD phenom x6.
Below is the output of serial console of a failed boot.
--
Sander
[ __ __ _ _ ___ _ _ _
\ \/ /___ _ __ | || | / _ \ _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ '_ \ | || || (_) |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | |__ _\__, |__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |_|(_)/_/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
(XEN) Xen version 4.9-unstable (root@dyndns.org) (gcc-4.9.real (Debian 4.9.2-10) 4.9.2) debug=y Thu Mar 2 15:20:24 CET 2017
(XEN) Latest ChangeSet: Fri Feb 17 17:10:50 2017 +0000 git:5cecf60
(XEN) Console output is synchronous.
(XEN) Bootloader: GRUB 2.02~beta2-22+deb8u1
(XEN) Command line: dom0_mem=2048M,max:2048M loglvl=all loglvl_guest=all console_timestamps=datems vga=gfx-1280x1024x32 no-cpuidle cpufreq=xen com1=38400,8n1 console=vga,com1 ivrs_ioapic[6]=00:14.0 iommu=on,verbose,debug,amd-iommu-debug conring_size=128k ucode=-1 sched=credit2 sync_console no-reboot
(XEN) Video information:
(XEN) VGA is graphics mode 1280x1024, 32 bpp
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 3 MBR signatures
(XEN) Found 3 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000097c00 (usable)
(XEN) 0000000000097c00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000c7f90000 (usable)
(XEN) 00000000c7f90000 - 00000000c7f9e000 (ACPI data)
(XEN) 00000000c7f9e000 - 00000000c7fe0000 (ACPI NVS)
(XEN) 00000000c7fe0000 - 00000000c8000000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000538000000 (usable)
(XEN) ACPI: RSDP 000FB100, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT C7F90000, 0048 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: FACP C7F90200, 0084 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: DSDT C7F905E0, 9427 (r1 A7640 A7640100 100 INTL 20051117)
(XEN) ACPI: FACS C7F9E000, 0040
(XEN) ACPI: APIC C7F90390, 0088 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: MCFG C7F90420, 003C (r1 7640MS OEMMCFG 20100913 MSFT 97)
(XEN) ACPI: SLIC C7F90460, 0176 (r1 MSI OEMSLIC 20100913 MSFT 97)
(XEN) ACPI: OEMB C7F9E040, 0072 (r1 7640MS A7640100 20100913 MSFT 97)
(XEN) ACPI: SRAT C7F9A5E0, 0108 (r3 AMD FAM_F_10 2 AMD 1)
(XEN) ACPI: HPET C7F9A6F0, 0038 (r1 7640MS OEMHPET 20100913 MSFT 97)
(XEN) ACPI: IVRS C7F9A730, 0100 (r1 AMD RD890S 202031 AMD 0)
(XEN) ACPI: SSDT C7F9A830, 0DA4 (r1 A M I POWERNOW 1 AMD 1)
(XEN) System RAM: 20479MB (20970652kB)
(XEN) SRAT: PXM 0 -> APIC 00 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 01 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 02 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 03 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 04 -> Node 0
(XEN) SRAT: PXM 0 -> APIC 05 -> Node 0
(XEN) SRAT: Node 0 PXM 0 0-a0000
(XEN) SRAT: Node 0 PXM 0 100000-c8000000
(XEN) SRAT: Node 0 PXM 0 100000000-538000000
(XEN) NUMA: Allocated memnodemap from 52a353000 - 52a359000
(XEN) NUMA: Using 8 for the hash shift.
(XEN) Domain heap initialised
(XEN) Allocated console ring of 128 KiB.
(XEN) vesafb: framebuffer at 0xd0000000, mapped to 0xffff82c000201000, using 6144k, total 16384k
(XEN) vesafb: mode is 1280x1024x32, linelength=5120, font 8x16
(XEN) vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
(XEN) CPU Vendor: AMD, Family 16 (0x10), Model 10 (0xa), Stepping 0 (raw 00100fa0)
(XEN) found SMP MP-table at 000ff780
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x808 (24 bits)
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:804,1:0], pm1x_evt[1:800,1:0]
(XEN) ACPI: wakeup_vec[c7f9e00c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 2 I/O APICs
(XEN) ACPI: HPET id: 0x8300 base: 0xfed00000
(XEN) ERST table was not found
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 6 CPUs (0 hotplug CPUs)
(XEN) IRQ limits: 56 GSI, 1112 MSI/MSI-X
(XEN) CPU0: AMD Fam10h machine check reporting enabled
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) load_precision_shift: 18
(XEN) load_window_shift: 30
(XEN) underload_balance_tolerance: 0
(XEN) overload_balance_tolerance: -3
(XEN) runqueues arrangement: socket
(XEN) load tracking window length 1073741824 ns
(XEN) Adding cpu 0 to runqueue 0
(XEN) First cpu on runqueue, activating
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 3200.111 MHz processor.
(XEN) Freed 1024kB unused BSS memory
(XEN) Initing memory sharing.
(XEN) alt table ffff82d0802f6a18 -> ffff82d0802f8080
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: Not using MCFG for segment 0000 bus 00-ff
(XEN) AMD-Vi: Found MSI capability block at 0x54
(XEN) AMD-Vi: IVRS Block: Found type 0x10 flags 0x3e len 0xd0 id 0x2
(XEN) AMD-Vi: Using IVHD type 0x10
(XEN) AMD-Vi: ACPI Table:
(XEN) AMD-Vi: Signature IVRS
(XEN) AMD-Vi: Length 0x100
(XEN) AMD-Vi: Revision 0x1
(XEN) AMD-Vi: CheckSum 0x29
(XEN) AMD-Vi: OEM_Id AMD
(XEN) AMD-Vi: OEM_Table_Id RD890S
(XEN) AMD-Vi: OEM_Revision 0x202031
(XEN) AMD-Vi: Creator_Id AMD
(XEN) AMD-Vi: Creator_Revision 0
(XEN) AMD-Vi: IVRS Block: type 0x10 flags 0x3e len 0xd0 id 0x2
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0 -> 0x2
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x10 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0xe00 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0xe00 -> 0xe01
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x18 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xd00 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x28 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xc00 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x30 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xb00 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x48 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa00 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x50 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x900 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x900 -> 0x907
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x60 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x500 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x608 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x800 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x610 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x700 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x68 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x400 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x88 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x90 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x90 -> 0x92
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x98 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x98 -> 0x9a
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa0 flags 0xd7
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa3 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa4 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x43 id 0x300 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0x300 -> 0x3ff alias 0xa4
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa5 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa8 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa9 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x100 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0xb0 flags 0
(XEN) AMD-Vi: Dev_Id Range: 0xb0 -> 0xb2
(XEN) AMD-Vi: IVHD Device Entry: type 0 id 0 flags 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
(XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
(XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
(XEN) AMD-Vi: Disabled HAP memory map sharing with IOMMU
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) nr_sockets: 1
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) [2017-03-02 14:28:28.440] microcode: CPU0 updated from revision 0x10000bf to 0x10000dc
(XEN) [2017-03-02 14:28:28.471] HVM: ASIDs enabled.
(XEN) [2017-03-02 14:28:28.491] SVM: Supported advanced features:
(XEN) [2017-03-02 14:28:28.515] - Nested Page Tables (NPT)
(XEN) [2017-03-02 14:28:28.538] - Last Branch Record (LBR) Virtualisation
(XEN) [2017-03-02 14:28:28.564] - Next-RIP Saved on #VMEXIT
(XEN) [2017-03-02 14:28:28.587] - Pause-Intercept Filter
(XEN) [2017-03-02 14:28:28.609] HVM: SVM enabled
(XEN) [2017-03-02 14:28:28.629] HVM: Hardware Assisted Paging (HAP) detected
(XEN) [2017-03-02 14:28:28.657] HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) [2017-03-02 14:28:28.681] HVM: PVH mode not supported on this platform
(XEN) [2017-03-02 14:28:28.729] Adding cpu 1 to runqueue 0
(XEN) [2017-03-02 14:28:28.752] microcode: CPU1 updated from revision 0x10000bf to 0x10000dc
(XEN) [2017-03-02 14:28:28.784] Adding cpu 2 to runqueue 0
(XEN) [2017-03-02 14:28:28.806] microcode: CPU2 updated from revision 0x10000bf to 0x10000dc
(XEN) [2017-03-02 14:28:28.858] Adding cpu 3 to runqueue 0
(XEN) [2017-03-02 14:28:28.881] microcode: CPU3 updated from revision 0x10000bf to 0x10000dc
(XEN) [2017-03-02 14:28:28.934] Adding cpu 4 to runqueue 0
(XEN) [2017-03-02 14:28:28.957] microcode: CPU4 updated from revision 0x10000bf to 0x10000dc
(XEN) [2017-03-02 14:28:29.009] Adding cpu 5 to runqueue 0
(XEN) [2017-03-02 14:28:29.032] Brought up 6 CPUs
(XEN) [2017-03-02 14:28:29.053] microcode: CPU5 updated from revision 0x10000bf to 0x10000dc
(XEN) [2017-03-02 14:28:29.089] build-id: 167b048e7b1949fca7aa5d75c980074f438cfa54
(XEN) [2017-03-02 14:28:29.119] traps.c:3452: GPF (0000): ffff82d0bffff041 [ffff82d0bffff041] -> ffff82d08024d23a
(XEN) [2017-03-02 14:28:29.157] traps.c:813: Trap 12: ffff82d0bffff040 [ffff82d0bffff040] -> ffff82d08024d23a
(XEN) [2017-03-02 14:28:29.214] ACPI sleep modes: S3
(XEN) [2017-03-02 14:28:29.236] VPMU: disabled
(XEN) [2017-03-02 14:28:29.256] MCA: Use hw thresholding to adjust polling frequency
(XEN) [2017-03-02 14:28:29.287] mcheck_poll: Machine check polling timer started.
(XEN) [2017-03-02 14:28:29.317] Xenoprofile: Failed to setup IBS LVT offset, IBSCTL = 0xffffffff
(XEN) [2017-03-02 14:28:29.350] Dom0 has maximum 632 PIRQs
(XEN) [2017-03-02 14:28:29.374] NX (Execute Disable) protection active
(XEN) [2017-03-02 14:28:29.401] *** LOADING DOMAIN 0 ***
(XEN) [2017-03-02 14:28:29.606] ELF: phdr: paddr=0x1000000 memsz=0x1290000
(XEN) [2017-03-02 14:28:29.634] ELF: phdr: paddr=0x2400000 memsz=0x137000
(XEN) [2017-03-02 14:28:29.662] ELF: phdr: paddr=0x2537000 memsz=0x18ed8
(XEN) [2017-03-02 14:28:29.690] ELF: phdr: paddr=0x2550000 memsz=0x2d6000
(XEN) [2017-03-02 14:28:29.718] ELF: memory: 0x1000000 -> 0x2826000
(XEN) [2017-03-02 14:28:29.744] ELF: note: GUEST_OS = "linux"
(XEN) [2017-03-02 14:28:29.769] ELF: note: GUEST_VERSION = "2.6"
(XEN) [2017-03-02 14:28:29.795] ELF: note: XEN_VERSION = "xen-3.0"
(XEN) [2017-03-02 14:28:29.821] ELF: note: VIRT_BASE = 0xffffffff80000000
(XEN) [2017-03-02 14:28:29.849] ELF: note: INIT_P2M = 0x8000000000
(XEN) [2017-03-02 14:28:29.875] ELF: note: ENTRY = 0xffffffff82550180
(XEN) [2017-03-02 14:28:29.903] ELF: note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) [2017-03-02 14:28:29.932] ELF: note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) [2017-03-02 14:28:29.967] ELF: note: SUPPORTED_FEATURES = 0x801
(XEN) [2017-03-02 14:28:29.994] ELF: note: PAE_MODE = "yes"
(XEN) [2017-03-02 14:28:30.019] ELF: note: LOADER = "generic"
(XEN) [2017-03-02 14:28:30.044] ELF: note: unknown (0xd)
(XEN) [2017-03-02 14:28:30.068] ELF: note: SUSPEND_CANCEL = 0x1
(XEN) [2017-03-02 14:28:30.094] ELF: note: MOD_START_PFN = 0x1
(XEN) [2017-03-02 14:28:30.119] ELF: note: HV_START_LOW = 0xffff800000000000
(XEN) [2017-03-02 14:28:30.148] ELF: note: PADDR_OFFSET = 0
(XEN) [2017-03-02 14:28:30.173] ELF: note: PHYS32_ENTRY = 0x10002d0
(XEN) [2017-03-02 14:28:30.200] ELF: addresses:
(XEN) [2017-03-02 14:28:30.222] virt_base = 0xffffffff80000000
(XEN) [2017-03-02 14:28:30.251] elf_paddr_offset = 0x0
(XEN) [2017-03-02 14:28:30.275] virt_offset = 0xffffffff80000000
(XEN) [2017-03-02 14:28:30.304] virt_kstart = 0xffffffff81000000
(XEN) [2017-03-02 14:28:30.333] virt_kend = 0xffffffff82826000
(XEN) [2017-03-02 14:28:30.362] virt_entry = 0xffffffff82550180
(XEN) [2017-03-02 14:28:30.391] p2m_base = 0x8000000000
(XEN) [2017-03-02 14:28:30.419] Xen kernel: 64-bit, lsb, compat32
(XEN) [2017-03-02 14:28:30.446] Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2826000
(XEN) [2017-03-02 14:28:30.481] PHYSICAL MEMORY ARRANGEMENT:
(XEN) [2017-03-02 14:28:30.506] Dom0 alloc.: 0000000520000000->0000000524000000 (501685 pages to be allocated)
(XEN) [2017-03-02 14:28:30.546] Init. ramdisk: 00000005367b1000->0000000537ffba00
(XEN) [2017-03-02 14:28:30.578] VIRTUAL MEMORY ARRANGEMENT:
(XEN) [2017-03-02 14:28:30.603] Loaded kernel: ffffffff81000000->ffffffff82826000
(XEN) [2017-03-02 14:28:30.635] Init. ramdisk: 0000000000000000->0000000000000000
(XEN) [2017-03-02 14:28:30.667] Phys-Mach map: 0000008000000000->0000008000400000
(XEN) [2017-03-02 14:28:30.699] Start info: ffffffff82826000->ffffffff828264b4
(XEN) [2017-03-02 14:28:30.731] Page tables: ffffffff82827000->ffffffff82840000
(XEN) [2017-03-02 14:28:30.762] Boot stack: ffffffff82840000->ffffffff82841000
(XEN) [2017-03-02 14:28:30.794] TOTAL: ffffffff80000000->ffffffff82c00000
(XEN) [2017-03-02 14:28:30.826] ENTRY ADDRESS: ffffffff82550180
(XEN) [2017-03-02 14:28:30.854] Dom0 has maximum 6 VCPUs
(XEN) [2017-03-02 14:28:30.879] ELF: phdr 0 at 0xffffffff81000000 -> 0xffffffff82290000
(XEN) [2017-03-02 14:28:30.919] ELF: phdr 1 at 0xffffffff82400000 -> 0xffffffff82537000
(XEN) [2017-03-02 14:28:30.953] ELF: phdr 2 at 0xffffffff82537000 -> 0xffffffff8254fed8
(XEN) [2017-03-02 14:28:30.986] ELF: phdr 3 at 0xffffffff82550000 -> 0xffffffff8267e000
(XEN) [2017-03-02 14:28:32.215] AMD-Vi: Setup I/O page table: device id = 0, type = 0x6, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.262] AMD-Vi: Setup I/O page table: device id = 0x2, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.311] AMD-Vi: Setup I/O page table: device id = 0x10, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.359] AMD-Vi: Setup I/O page table: device id = 0x18, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.408] AMD-Vi: Setup I/O page table: device id = 0x28, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.457] AMD-Vi: Setup I/O page table: device id = 0x30, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.506] AMD-Vi: Setup I/O page table: device id = 0x48, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.556] AMD-Vi: Setup I/O page table: device id = 0x50, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.605] AMD-Vi: Setup I/O page table: device id = 0x60, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.655] AMD-Vi: Setup I/O page table: device id = 0x68, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.704] AMD-Vi: Setup I/O page table: device id = 0x88, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.754] AMD-Vi: Setup I/O page table: device id = 0x90, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.804] AMD-Vi: Setup I/O page table: device id = 0x92, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.854] AMD-Vi: Setup I/O page table: device id = 0x98, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.905] AMD-Vi: Setup I/O page table: device id = 0x9a, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:32.955] AMD-Vi: Setup I/O page table: device id = 0xa0, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.006] AMD-Vi: Setup I/O page table: device id = 0xa3, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.057] AMD-Vi: Setup I/O page table: device id = 0xa4, type = 0x5, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.108] AMD-Vi: Setup I/O page table: device id = 0xa5, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.159] AMD-Vi: Setup I/O page table: device id = 0xa8, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.211] AMD-Vi: Setup I/O page table: device id = 0xb0, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.262] AMD-Vi: Setup I/O page table: device id = 0xb2, type = 0x7, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.314] AMD-Vi: Skipping host bridge 0000:00:18.0
(XEN) [2017-03-02 14:28:33.347] AMD-Vi: Skipping host bridge 0000:00:18.1
(XEN) [2017-03-02 14:28:33.380] AMD-Vi: Skipping host bridge 0000:00:18.2
(XEN) [2017-03-02 14:28:33.414] AMD-Vi: Skipping host bridge 0000:00:18.3
(XEN) [2017-03-02 14:28:33.447] AMD-Vi: Skipping host bridge 0000:00:18.4
(XEN) [2017-03-02 14:28:33.480] AMD-Vi: Setup I/O page table: device id = 0x400, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.532] AMD-Vi: Setup I/O page table: device id = 0x500, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.584] AMD-Vi: Setup I/O page table: device id = 0x608, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.637] AMD-Vi: Setup I/O page table: device id = 0x610, type = 0x2, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.690] AMD-Vi: Setup I/O page table: device id = 0x700, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.743] AMD-Vi: Setup I/O page table: device id = 0x800, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.796] AMD-Vi: Setup I/O page table: device id = 0x900, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.850] AMD-Vi: Setup I/O page table: device id = 0x901, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.903] AMD-Vi: Setup I/O page table: device id = 0x902, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:33.957] AMD-Vi: Setup I/O page table: device id = 0x903, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.011] AMD-Vi: Setup I/O page table: device id = 0x904, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.065] AMD-Vi: Setup I/O page table: device id = 0x905, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.120] AMD-Vi: Setup I/O page table: device id = 0x906, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.174] AMD-Vi: Setup I/O page table: device id = 0x907, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.229] AMD-Vi: Setup I/O page table: device id = 0xa00, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.284] AMD-Vi: Setup I/O page table: device id = 0xb00, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.339] AMD-Vi: Setup I/O page table: device id = 0xc00, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.394] AMD-Vi: Setup I/O page table: device id = 0xd00, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.449] AMD-Vi: Setup I/O page table: device id = 0xe00, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.505] AMD-Vi: Setup I/O page table: device id = 0xe01, type = 0x1, root table = 0x526158000, domain = 0, paging mode = 3
(XEN) [2017-03-02 14:28:34.569] Scrubbing Free RAM on 1 nodes using 6 CPUs
(XEN) [2017-03-02 14:28:34.691] ............................done.
(XEN) [2017-03-02 14:28:37.703] Initial low memory virq threshold set at 0x4000 pages.
(XEN) [2017-03-02 14:28:37.743] Std. Loglevel: All
(XEN) [2017-03-02 14:28:37.774] Guest Loglevel: All
(XEN) [2017-03-02 14:28:37.805] ***************************************************
(XEN) [2017-03-02 14:28:37.844] WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) [2017-03-02 14:28:37.879] This option is intended to aid debugging of Xen by ensuring
(XEN) [2017-03-02 14:28:37.921] that all output is synchronously delivered on the serial line.
(XEN) [2017-03-02 14:28:37.963] However it can introduce SIGNIFICANT latencies and affect
(XEN) [2017-03-02 14:28:38.003] timekeeping. It is NOT recommended for production use!
(XEN) [2017-03-02 14:28:38.043] ***************************************************
(XEN) [2017-03-02 14:28:38.083] 3... 2... 1...
(XEN) [2017-03-02 14:28:41.112] Xen is relinquishing VGA console.
(XEN) [2017-03-02 14:28:41.230] *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) [2017-03-02 14:28:41.258] Freed 348kB init memory
mapping kernel into physical memory
about to get started...
[ 0.000000] Linux version 4.10.0-20170220-linus-doflr-xennext+ (root@serveerstertje) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Mon Feb 20 15:52:10 CET 2017
[ 0.000000] Command line: root=/dev/mapper/serveerstertje_ssd-root ro verbose earlyprintk=xen mem=2048M console=hvc0 console=tty0 acpi_enforce_resources=lax max_loop=30 loop_max_part=10 r8169.use_dac=1 loglevel=10 nomodeset xen-pciback.hide=(03:06.0)(04:00.0)(08:00.0)(09:00.*)(0d:00.0)
[ 0.000000] x86/fpu: Legacy x87 FPU detected.
[ 0.000000] Released 0 page(s)
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] Xen: [mem 0x0000000000000000-0x0000000000096fff] usable
[ 0.000000] Xen: [mem 0x0000000000097c00-0x00000000000fffff] reserved
[ 0.000000] Xen: [mem 0x0000000000100000-0x0000000080068fff] usable
[ 0.000000] Xen: [mem 0x00000000c7f90000-0x00000000c7f9dfff] ACPI data
[ 0.000000] Xen: [mem 0x00000000c7f9e000-0x00000000c7fdffff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000c7fe0000-0x00000000c7ffffff] reserved
[ 0.000000] Xen: [mem 0x00000000f6000000-0x00000000f6003fff] reserved
[ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] Xen: [mem 0x00000000fec20000-0x00000000fec20fff] reserved
[ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000feefffff] reserved
[ 0.000000] Xen: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
[ 0.000000] Xen: [mem 0x000000fd00000000-0x000000ffffffffff] reserved
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] e820: user-defined physical RAM map:
[ 0.000000] user: [mem 0x0000000000000000-0x0000000000096fff] usable
[ 0.000000] user: [mem 0x0000000000097c00-0x00000000000fffff] reserved
[ 0.000000] user: [mem 0x0000000000100000-0x000000007fffffff] usable
[ 0.000000] user: [mem 0x00000000c7f90000-0x00000000c7f9dfff] ACPI data
[ 0.000000] user: [mem 0x00000000c7f9e000-0x00000000c7fdffff] ACPI NVS
[ 0.000000] user: [mem 0x00000000c7fe0000-0x00000000c7ffffff] reserved
[ 0.000000] user: [mem 0x00000000f6000000-0x00000000f6003fff] reserved
[ 0.000000] user: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] user: [mem 0x00000000fec20000-0x00000000fec20fff] reserved
[ 0.000000] user: [mem 0x00000000fee00000-0x00000000feefffff] reserved
[ 0.000000] user: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
[ 0.000000] user: [mem 0x000000fd00000000-0x000000ffffffffff] reserved
[ 0.000000] SMBIOS 2.5 present.
[ 0.000000] DMI: MSI MS-7640/890FXA-GD70 (MS-7640) , BIOS V1.8B1 09/13/2010
[ 0.000000] Hypervisor detected: Xen
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] e820: last_pfn = 0x80000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR: Disabled
[ 0.000000] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WC WP UC UC
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000091000] 91000 size 24576
[ 0.000000] BRK [0x02800000, 0x02800fff] PGTABLE
[ 0.000000] BRK [0x02801000, 0x02801fff] PGTABLE
[ 0.000000] BRK [0x02802000, 0x02802fff] PGTABLE
[ 0.000000] BRK [0x02803000, 0x02803fff] PGTABLE
[ 0.000000] BRK [0x02804000, 0x02804fff] PGTABLE
[ 0.000000] BRK [0x02805000, 0x02805fff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x04000000-0x0584afff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000FB100 000014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 0x00000000C7F90000 000048 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: FACP 0x00000000C7F90200 000084 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: DSDT 0x00000000C7F905E0 009427 (v01 A7640 A7640100 00000100 INTL 20051117)
[ 0.000000] ACPI: FACS 0x00000000C7F9E000 000040
[ 0.000000] ACPI: APIC 0x00000000C7F90390 000088 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: MCFG 0x00000000C7F90420 00003C (v01 7640MS OEMMCFG 20100913 MSFT 00000097)
[ 0.000000] ACPI: SLIC 0x00000000C7F90460 000176 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: OEMB 0x00000000C7F9E040 000072 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: SRAT 0x00000000C7F9A5E0 000108 (v03 AMD FAM_F_10 00000002 AMD 00000001)
[ 0.000000] ACPI: HPET 0x00000000C7F9A6F0 000038 (v01 7640MS OEMHPET 20100913 MSFT 00000097)
[ 0.000000] ACPI: IVRS 0x00000000C7F9A730 000100 (v01 AMD RD890S 00202031 AMD 00000000)
[ 0.000000] ACPI: SSDT 0x00000000C7F9A830 000DA4 (v01 A M I POWERNOW 00000001 AMD 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] Setting APIC routing to Xen PV.
[ 0.000000] NUMA turned off
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x7fc11000-0x7fc1afff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x000000007fffffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x0000000000096fff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x000000007fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000007fffffff]
[ 0.000000] On node 0 totalpages: 524182
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3990 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 8128 pages used for memmap
[ 0.000000] DMA32 zone: 520192 pages, LIFO batch:31
[ 0.000000] p2m virtual area at ffffc90000000000, size is 600000
[ 0.000000] Remapped 105 page(s)
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
[ 0.000000] IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8300 base: 0xfed00000
[ 0.000000] smpboot: Allowing 6 CPUs, 0 hotplug CPUs
[ 0.000000] e820: [mem 0x80000000-0xc7f8ffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.9-unstable (preserve-AD)
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
[ 0.000000] setup_percpu: NR_CPUS:6 nr_cpumask_bits:6 nr_cpu_ids:6 nr_node_ids:1
[ 0.000000] percpu: Embedded 34 pages/cpu @ffff88007d000000 s102104 r8192 d28968 u262144
[ 0.000000] pcpu-alloc: s102104 r8192 d28968 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 - -
[ 0.000000] xen: PV spinlocks enabled
[ 0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 515969
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: root=/dev/mapper/serveerstertje_ssd-root ro verbose earlyprintk=xen mem=2048M console=hvc0 console=tty0 acpi_enforce_resources=lax max_loop=30 loop_max_part=10 r8169.use_dac=1 loglevel=10 nomodeset xen-pciback.hide=(03:06.0)(04:00.0)(08:00.0)(09:00.*)(0d:00.0)
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] software IO TLB [mem 0x79000000-0x7d000000] (64MB) mapped at [ffff880079000000-ffff88007cffffff]
[ 0.000000] Memory: 1939208K/2096728K available (12983K kernel code, 1239K rwdata, 4672K rodata, 1264K init, 1540K bss, 157520K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] Using NULL legacy PIC
[ 0.000000] NR_IRQS:4352 nr_irqs:1016 0
[ 0.000000] xen:events: Using FIFO-based ABI
[ 0.000000] xen: --> pirq=1 -> irq=1 (gsi=1)
[ 0.000000] xen: --> pirq=2 -> irq=2 (gsi=2)
[ 0.000000] xen: --> pirq=3 -> irq=3 (gsi=3)
[ 0.000000] xen: --> pirq=4 -> irq=4 (gsi=4)
[ 0.000000] xen: --> pirq=5 -> irq=5 (gsi=5)
[ 0.000000] xen: --> pirq=6 -> irq=6 (gsi=6)
[ 0.000000] xen: --> pirq=7 -> irq=7 (gsi=7)
[ 0.000000] xen: --> pirq=8 -> irq=8 (gsi=8)
[ 0.000000] xen: --> pirq=9 -> irq=9 (gsi=9)
[ 0.000000] xen: --> pirq=10 -> irq=10 (gsi=10)
[ 0.000000] xen: --> pirq=11 -> irq=11 (gsi=11)
[ 0.000000] xen: --> pirq=12 -> irq=12 (gsi=12)
[ 0.000000] xen: --> pirq=13 -> irq=13 (gsi=13)
[ 0.000000] xen: --> pirq=14 -> irq=14 (gsi=14)
[ 0.000000] xen: --> pirq=15 -> irq=15 (gsi=15)
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] bootconsole [xenboot0] disabled
[ 0.000000] Linux version 4.10.0-20170220-linus-doflr-xennext+ (root@serveerstertje) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Mon Feb 20 15:52:10 CET 2017
[ 0.000000] Command line: root=/dev/mapper/serveerstertje_ssd-root ro verbose earlyprintk=xen mem=2048M console=hvc0 console=tty0 acpi_enforce_resources=lax max_loop=30 loop_max_part=10 r8169.use_dac=1 loglevel=10 nomodeset xen-pciback.hide=(03:06.0)(04:00.0)(08:00.0)(09:00.*)(0d:00.0)
[ 0.000000] x86/fpu: Legacy x87 FPU detected.
[ 0.000000] Released 0 page(s)
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] Xen: [mem 0x0000000000000000-0x0000000000096fff] usable
[ 0.000000] Xen: [mem 0x0000000000097c00-0x00000000000fffff] reserved
[ 0.000000] Xen: [mem 0x0000000000100000-0x0000000080068fff] usable
[ 0.000000] Xen: [mem 0x00000000c7f90000-0x00000000c7f9dfff] ACPI data
[ 0.000000] Xen: [mem 0x00000000c7f9e000-0x00000000c7fdffff] ACPI NVS
[ 0.000000] Xen: [mem 0x00000000c7fe0000-0x00000000c7ffffff] reserved
[ 0.000000] Xen: [mem 0x00000000f6000000-0x00000000f6003fff] reserved
[ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] Xen: [mem 0x00000000fec20000-0x00000000fec20fff] reserved
[ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000feefffff] reserved
[ 0.000000] Xen: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
[ 0.000000] Xen: [mem 0x000000fd00000000-0x000000ffffffffff] reserved
[ 0.000000] bootconsole [xenboot0] enabled
[ 0.000000] e820: remove [mem 0x80000000-0xfffffffffffffffe] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] e820: user-defined physical RAM map:
[ 0.000000] user: [mem 0x0000000000000000-0x0000000000096fff] usable
[ 0.000000] user: [mem 0x0000000000097c00-0x00000000000fffff] reserved
[ 0.000000] user: [mem 0x0000000000100000-0x000000007fffffff] usable
[ 0.000000] user: [mem 0x00000000c7f90000-0x00000000c7f9dfff] ACPI data
[ 0.000000] user: [mem 0x00000000c7f9e000-0x00000000c7fdffff] ACPI NVS
[ 0.000000] user: [mem 0x00000000c7fe0000-0x00000000c7ffffff] reserved
[ 0.000000] user: [mem 0x00000000f6000000-0x00000000f6003fff] reserved
[ 0.000000] user: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] user: [mem 0x00000000fec20000-0x00000000fec20fff] reserved
[ 0.000000] user: [mem 0x00000000fee00000-0x00000000feefffff] reserved
[ 0.000000] user: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
[ 0.000000] user: [mem 0x000000fd00000000-0x000000ffffffffff] reserved
[ 0.000000] SMBIOS 2.5 present.
[ 0.000000] DMI: MSI MS-7640/890FXA-GD70 (MS-7640) , BIOS V1.8B1 09/13/2010
[ 0.000000] Hypervisor detected: Xen
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] e820: last_pfn = 0x80000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR: Disabled
[ 0.000000] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[ 0.000000] x86/PAT: Configuration [0-7]: WB WT UC- UC WC WP UC UC
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000091000] 91000 size 24576
[ 0.000000] BRK [0x02800000, 0x02800fff] PGTABLE
[ 0.000000] BRK [0x02801000, 0x02801fff] PGTABLE
[ 0.000000] BRK [0x02802000, 0x02802fff] PGTABLE
[ 0.000000] BRK [0x02803000, 0x02803fff] PGTABLE
[ 0.000000] BRK [0x02804000, 0x02804fff] PGTABLE
[ 0.000000] BRK [0x02805000, 0x02805fff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x04000000-0x0584afff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000FB100 000014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 0x00000000C7F90000 000048 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: FACP 0x00000000C7F90200 000084 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: DSDT 0x00000000C7F905E0 009427 (v01 A7640 A7640100 00000100 INTL 20051117)
[ 0.000000] ACPI: FACS 0x00000000C7F9E000 000040
[ 0.000000] ACPI: APIC 0x00000000C7F90390 000088 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: MCFG 0x00000000C7F90420 00003C (v01 7640MS OEMMCFG 20100913 MSFT 00000097)
[ 0.000000] ACPI: SLIC 0x00000000C7F90460 000176 (v01 MSI OEMSLIC 20100913 MSFT 00000097)
[ 0.000000] ACPI: OEMB 0x00000000C7F9E040 000072 (v01 7640MS A7640100 20100913 MSFT 00000097)
[ 0.000000] ACPI: SRAT 0x00000000C7F9A5E0 000108 (v03 AMD FAM_F_10 00000002 AMD 00000001)
[ 0.000000] ACPI: HPET 0x00000000C7F9A6F0 000038 (v01 7640MS OEMHPET 20100913 MSFT 00000097)
[ 0.000000] ACPI: IVRS 0x00000000C7F9A730 000100 (v01 AMD RD890S 00202031 AMD 00000000)
[ 0.000000] ACPI: SSDT 0x00000000C7F9A830 000DA4 (v01 A M I POWERNOW 00000001 AMD 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] Setting APIC routing to Xen PV.
[ 0.000000] NUMA turned off
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x7fc11000-0x7fc1afff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x000000007fffffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x0000000000096fff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x000000007fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000007fffffff]
[ 0.000000] On node 0 totalpages: 524182
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3990 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 8128 pages used for memmap
[ 0.000000] DMA32 zone: 520192 pages, LIFO batch:31
[ 0.000000] p2m virtual area at ffffc90000000000, size is 600000
[ 0.000000] Remapped 105 page(s)
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
[ 0.000000] IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8300 base: 0xfed00000
[ 0.000000] smpboot: Allowing 6 CPUs, 0 hotplug CPUs
[ 0.000000] e820: [mem 0x80000000-0xc7f8ffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on Xen
[ 0.000000] Xen version: 4.9-unstable (preserve-AD)
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns
[ 0.000000] setup_percpu: NR_CPUS:6 nr_cpumask_bits:6 nr_cpu_ids:6 nr_node_ids:1
[ 0.000000] percpu: Embedded 34 pages/cpu @ffff88007d000000 s102104 r8192 d28968 u262144
[ 0.000000] pcpu-alloc: s102104 r8192 d28968 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 - -
[ 0.000000] xen: PV spinlocks enabled
[ 0.000000] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes)
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 515969
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: root=/dev/mapper/serveerstertje_ssd-root ro verbose earlyprintk=xen mem=2048M console=hvc0 console=tty0 acpi_enforce_resources=lax max_loop=30 loop_max_part=10 r8169.use_dac=1 loglevel=10 nomodeset xen-pciback.hide=(03:06.0)(04:00.0)(08:00.0)(09:00.*)(0d:00.0)
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] software IO TLB [mem 0x79000000-0x7d000000] (64MB) mapped at [ffff880079000000-ffff88007cffffff]
[ 0.000000] Memory: 1939208K/2096728K available (12983K kernel code, 1239K rwdata, 4672K rodata, 1264K init, 1540K bss, 157520K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] Using NULL legacy PIC
[ 0.000000] NR_IRQS:4352 nr_irqs:1016 0
[ 0.000000] xen:events: Using FIFO-based ABI
[ 0.000000] xen: --> pirq=1 -> irq=1 (gsi=1)
[ 0.000000] xen: --> pirq=2 -> irq=2 (gsi=2)
[ 0.000000] xen: --> pirq=3 -> irq=3 (gsi=3)
[ 0.000000] xen: --> pirq=4 -> irq=4 (gsi=4)
[ 0.000000] xen: --> pirq=5 -> irq=5 (gsi=5)
[ 0.000000] xen: --> pirq=6 -> irq=6 (gsi=6)
[ 0.000000] xen: --> pirq=7 -> irq=7 (gsi=7)
[ 0.000000] xen: --> pirq=8 -> irq=8 (gsi=8)
[ 0.000000] xen: --> pirq=9 -> irq=9 (gsi=9)
[ 0.000000] xen: --> pirq=10 -> irq=10 (gsi=10)
[ 0.000000] xen: --> pirq=11 -> irq=11 (gsi=11)
[ 0.000000] xen: --> pirq=12 -> irq=12 (gsi=12)
[ 0.000000] xen: --> pirq=13 -> irq=13 (gsi=13)
[ 0.000000] xen: --> pirq=14 -> irq=14 (gsi=14)
[ 0.000000] xen: --> pirq=15 -> irq=15 (gsi=15)
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] bootconsole [xenboot0] disabled
[ 0.000000] console [hvc0] enabled
[ 0.000000] clocksource: xen: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[ 0.000000] Xen: using vcpuop timer interface
[ 0.000000] installing Xen timer for CPU 0
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 3200.100 MHz processor
[ 22.296698] Calibrating delay loop (skipped), value calculated using timer frequency.. 6402.89 BogoMIPS (lpj=10667033)
[ 22.328857] pid_max: default: 32768 minimum: 301
[ 22.342900] ACPI: Core revision 20160930
[ 22.371164] ACPI: 2 ACPI AML tables successfully acquired and loaded
[ 22.390443] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 22.412237] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 22.433388] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 22.453368] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[ 22.475216] CPU: Physical Processor ID: 0
[ 22.487162] CPU: Processor Core ID: 0
[ 22.498344] mce: CPU supports 2 MCE banks
[ 22.510572] Last level iTLB entries: 4KB 512, 2MB 16, 4MB 8
[ 22.527456] Last level dTLB entries: 4KB 512, 2MB 128, 4MB 64, 1GB 0
[ 22.546832] Freeing SMP alternatives memory: 44K
[ 22.563865] cpu 0 spinlock event irq 57
[ 22.575110] smpboot: Max logical packages: 1
[ 22.588094] VPMU disabled by hypervisor.
[ 22.600121] Performance Events: PMU not available due to virtualization, using software events only.
[ 22.627816] NMI watchdog: disabled (cpu0): hardware events not enabled
[ 22.647368] NMI watchdog: Shutting down hard lockup detector on all cpus
[ 22.667658] smp: Bringing up secondary CPUs ...
[ 22.681523] installing Xen timer for CPU 1
[ 22.694322] cpu 1 spinlock event irq 69
[ 22.705777] installing Xen timer for CPU 2
[ 22.718473] cpu 2 spinlock event irq 76
[ 22.729937] installing Xen timer for CPU 3
[ 22.742614] cpu 3 spinlock event irq 83
[ 22.754101] installing Xen timer for CPU 4
(XEN) [2017-03-02 14:28:47.009] Hardware Dom0 crashed: 'noreboot' set - not rebooting.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 14:42 Xen-unstable: Bisected Host boot failure on AMD Phenom Sander Eikelenboom
@ 2017-03-02 14:55 ` Andrew Cooper
2017-03-02 17:29 ` Sander Eikelenboom
0 siblings, 1 reply; 14+ messages in thread
From: Andrew Cooper @ 2017-03-02 14:55 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
On 02/03/17 14:42, Sander Eikelenboom wrote:
> Hi Andrew / Jan,
>
> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
> Bisection has turned up:
> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
> Author: Andrew Cooper <andrew.cooper3@citrix.com>
> Date: Fri Feb 17 17:10:50 2017 +0000
>
> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>
> Hardware is a AMD phenom x6.
> Below is the output of serial console of a failed boot.
Hmm. Sorry for breaking this (although my AMD servers are booting fine).
It is unfortunately not entirely obvious what Linux is objecting to, and
must be related to something visible in the emulated view.
Does this delta make any difference?
diff --git a/xen/arch/x86/cpuid.c b/xen/arch/x86/cpuid.c
index 0dd35dc..c8fabe9 100644
--- a/xen/arch/x86/cpuid.c
+++ b/xen/arch/x86/cpuid.c
@@ -747,9 +747,14 @@ void guest_cpuid(const struct vcpu *v, uint32_t leaf,
const struct cpu_user_regs *regs;
case 0x1:
- /* TODO: Rework topology logic. */
- res->b &= 0x00ffffffu;
- res->b |= (v->vcpu_id * 2) << 24;
+ if ( is_hardware_domain(d) )
+ res->b = cpuid_ebx(0x1);
+ else
+ {
+ /* TODO: Rework topology logic. */
+ res->b &= 0x00ffffffu;
+ res->b |= (v->vcpu_id * 2) << 24;
+ }
/* TODO: Rework vPMU control in terms of toolstack choices. */
if ( vpmu_available(v) &&
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 14:55 ` Andrew Cooper
@ 2017-03-02 17:29 ` Sander Eikelenboom
2017-03-02 17:38 ` Andrew Cooper
0 siblings, 1 reply; 14+ messages in thread
From: Sander Eikelenboom @ 2017-03-02 17:29 UTC (permalink / raw)
To: Andrew Cooper; +Cc: Jan Beulich, xen-devel
On 02/03/17 15:55, Andrew Cooper wrote:
> On 02/03/17 14:42, Sander Eikelenboom wrote:
>> Hi Andrew / Jan,
>>
>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>> Bisection has turned up:
>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>> Date: Fri Feb 17 17:10:50 2017 +0000
>>
>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>
>> Hardware is a AMD phenom x6.
>> Below is the output of serial console of a failed boot.
>
> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
No problem, it is the staging branch of the unstable tree anyway ;-)
> It is unfortunately not entirely obvious what Linux is objecting to, and
> must be related to something visible in the emulated view.
>
> Does this delta make any difference?
Yes it does, boots fine with this patch applied, thanks !
--
Sander
>
> diff --git a/xen/arch/x86/cpuid.c b/xen/arch/x86/cpuid.c
> index 0dd35dc..c8fabe9 100644
> --- a/xen/arch/x86/cpuid.c
> +++ b/xen/arch/x86/cpuid.c
> @@ -747,9 +747,14 @@ void guest_cpuid(const struct vcpu *v, uint32_t leaf,
> const struct cpu_user_regs *regs;
>
> case 0x1:
> - /* TODO: Rework topology logic. */
> - res->b &= 0x00ffffffu;
> - res->b |= (v->vcpu_id * 2) << 24;
> + if ( is_hardware_domain(d) )
> + res->b = cpuid_ebx(0x1);
> + else
> + {
> + /* TODO: Rework topology logic. */
> + res->b &= 0x00ffffffu;
> + res->b |= (v->vcpu_id * 2) << 24;
> + }
>
> /* TODO: Rework vPMU control in terms of toolstack choices. */
> if ( vpmu_available(v) &&
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 17:29 ` Sander Eikelenboom
@ 2017-03-02 17:38 ` Andrew Cooper
2017-03-02 18:25 ` Sander Eikelenboom
0 siblings, 1 reply; 14+ messages in thread
From: Andrew Cooper @ 2017-03-02 17:38 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
On 02/03/17 17:29, Sander Eikelenboom wrote:
> On 02/03/17 15:55, Andrew Cooper wrote:
>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>> Hi Andrew / Jan,
>>>
>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>> Bisection has turned up:
>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>
>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>
>>> Hardware is a AMD phenom x6.
>>> Below is the output of serial console of a failed boot.
>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
> No problem, it is the staging branch of the unstable tree anyway ;-)
>
>> It is unfortunately not entirely obvious what Linux is objecting to, and
>> must be related to something visible in the emulated view.
>>
>> Does this delta make any difference?
> Yes it does, boots fine with this patch applied, thanks !
That is bad though. :s
It means that something in dom0 has an aversion to my attempt to lie
less about the topology.
Do you mind checking whether
res->b = cpuid_ebx(0x1) & 0xff00ffffu;
causes is to break again?
That will confirm whether the breakage is to do with Logical Processors
Per Package (which I suspect is the case), or the APIC ID field (which
has always been unstable in the past).
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 17:38 ` Andrew Cooper
@ 2017-03-02 18:25 ` Sander Eikelenboom
2017-03-02 18:29 ` Andrew Cooper
0 siblings, 1 reply; 14+ messages in thread
From: Sander Eikelenboom @ 2017-03-02 18:25 UTC (permalink / raw)
To: Andrew Cooper; +Cc: Jan Beulich, xen-devel
On 02/03/17 18:38, Andrew Cooper wrote:
> On 02/03/17 17:29, Sander Eikelenboom wrote:
>> On 02/03/17 15:55, Andrew Cooper wrote:
>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>> Hi Andrew / Jan,
>>>>
>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>> Bisection has turned up:
>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>
>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>
>>>> Hardware is a AMD phenom x6.
>>>> Below is the output of serial console of a failed boot.
>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>
>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>> must be related to something visible in the emulated view.
>>>
>>> Does this delta make any difference?
>> Yes it does, boots fine with this patch applied, thanks !
>
> That is bad though. :s
>
> It means that something in dom0 has an aversion to my attempt to lie
> less about the topology.
>
> Do you mind checking whether
>
> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>
> causes is to break again?
Used that in the is_hardware_domain() case and it boots fine.
--
Sander
> That will confirm whether the breakage is to do with Logical Processors
> Per Package (which I suspect is the case), or the APIC ID field (which
> has always been unstable in the past).
>
> ~Andrew
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 18:25 ` Sander Eikelenboom
@ 2017-03-02 18:29 ` Andrew Cooper
2017-03-02 18:51 ` Sander Eikelenboom
0 siblings, 1 reply; 14+ messages in thread
From: Andrew Cooper @ 2017-03-02 18:29 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
On 02/03/17 18:25, Sander Eikelenboom wrote:
> On 02/03/17 18:38, Andrew Cooper wrote:
>> On 02/03/17 17:29, Sander Eikelenboom wrote:
>>> On 02/03/17 15:55, Andrew Cooper wrote:
>>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>>> Hi Andrew / Jan,
>>>>>
>>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>>> Bisection has turned up:
>>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>>
>>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>>
>>>>> Hardware is a AMD phenom x6.
>>>>> Below is the output of serial console of a failed boot.
>>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>>
>>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>>> must be related to something visible in the emulated view.
>>>>
>>>> Does this delta make any difference?
>>> Yes it does, boots fine with this patch applied, thanks !
>> That is bad though. :s
>>
>> It means that something in dom0 has an aversion to my attempt to lie
>> less about the topology.
>>
>> Do you mind checking whether
>>
>> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>>
>> causes is to break again?
> Used that in the is_hardware_domain() case and it boots fine.
Hmm - curious. I am now even more confused.
What about this?
res->b = cpuid_ebx(0x1) & 0x00ffffffu;
It will leave the APIC_ID field zeroed rather than feeding v->vcpu_id
back into it.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 18:29 ` Andrew Cooper
@ 2017-03-02 18:51 ` Sander Eikelenboom
2017-03-02 18:56 ` Andrew Cooper
0 siblings, 1 reply; 14+ messages in thread
From: Sander Eikelenboom @ 2017-03-02 18:51 UTC (permalink / raw)
To: Andrew Cooper; +Cc: Jan Beulich, xen-devel
On 02/03/17 19:29, Andrew Cooper wrote:
> On 02/03/17 18:25, Sander Eikelenboom wrote:
>> On 02/03/17 18:38, Andrew Cooper wrote:
>>> On 02/03/17 17:29, Sander Eikelenboom wrote:
>>>> On 02/03/17 15:55, Andrew Cooper wrote:
>>>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>>>> Hi Andrew / Jan,
>>>>>>
>>>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>>>> Bisection has turned up:
>>>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>>>
>>>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>>>
>>>>>> Hardware is a AMD phenom x6.
>>>>>> Below is the output of serial console of a failed boot.
>>>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>>>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>>>
>>>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>>>> must be related to something visible in the emulated view.
>>>>>
>>>>> Does this delta make any difference?
>>>> Yes it does, boots fine with this patch applied, thanks !
>>> That is bad though. :s
>>>
>>> It means that something in dom0 has an aversion to my attempt to lie
>>> less about the topology.
>>>
>>> Do you mind checking whether
>>>
>>> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>>>
>>> causes is to break again?
>> Used that in the is_hardware_domain() case and it boots fine.
>
> Hmm - curious. I am now even more confused.
>
> What about this?
>
> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>
> It will leave the APIC_ID field zeroed rather than feeding v->vcpu_id
> back into it.
Also boots fine.
--
Sander
>
> ~Andrew
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 18:51 ` Sander Eikelenboom
@ 2017-03-02 18:56 ` Andrew Cooper
2017-03-02 19:15 ` Boris Ostrovsky
0 siblings, 1 reply; 14+ messages in thread
From: Andrew Cooper @ 2017-03-02 18:56 UTC (permalink / raw)
To: Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
On 02/03/17 18:51, Sander Eikelenboom wrote:
> On 02/03/17 19:29, Andrew Cooper wrote:
>> On 02/03/17 18:25, Sander Eikelenboom wrote:
>>> On 02/03/17 18:38, Andrew Cooper wrote:
>>>> On 02/03/17 17:29, Sander Eikelenboom wrote:
>>>>> On 02/03/17 15:55, Andrew Cooper wrote:
>>>>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>>>>> Hi Andrew / Jan,
>>>>>>>
>>>>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>>>>> Bisection has turned up:
>>>>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>>>>
>>>>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>>>>
>>>>>>> Hardware is a AMD phenom x6.
>>>>>>> Below is the output of serial console of a failed boot.
>>>>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>>>>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>>>>
>>>>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>>>>> must be related to something visible in the emulated view.
>>>>>>
>>>>>> Does this delta make any difference?
>>>>> Yes it does, boots fine with this patch applied, thanks !
>>>> That is bad though. :s
>>>>
>>>> It means that something in dom0 has an aversion to my attempt to lie
>>>> less about the topology.
>>>>
>>>> Do you mind checking whether
>>>>
>>>> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>>>>
>>>> causes is to break again?
>>> Used that in the is_hardware_domain() case and it boots fine.
>> Hmm - curious. I am now even more confused.
>>
>> What about this?
>>
>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>>
>> It will leave the APIC_ID field zeroed rather than feeding v->vcpu_id
>> back into it.
> Also boots fine.
Right. For my sanity, what about
res->b = cpuid_ebx(0x1) & 0x00ffffffu;
res->b |= (v->vcpu_id * 2) << 24;
?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 18:56 ` Andrew Cooper
@ 2017-03-02 19:15 ` Boris Ostrovsky
2017-03-02 19:17 ` Andrew Cooper
0 siblings, 1 reply; 14+ messages in thread
From: Boris Ostrovsky @ 2017-03-02 19:15 UTC (permalink / raw)
To: Andrew Cooper, Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
On 03/02/2017 01:56 PM, Andrew Cooper wrote:
> On 02/03/17 18:51, Sander Eikelenboom wrote:
>> On 02/03/17 19:29, Andrew Cooper wrote:
>>> On 02/03/17 18:25, Sander Eikelenboom wrote:
>>>> On 02/03/17 18:38, Andrew Cooper wrote:
>>>>> On 02/03/17 17:29, Sander Eikelenboom wrote:
>>>>>> On 02/03/17 15:55, Andrew Cooper wrote:
>>>>>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>>>>>> Hi Andrew / Jan,
>>>>>>>>
>>>>>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>>>>>> Bisection has turned up:
>>>>>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>>>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>>>>>
>>>>>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>>>>>
>>>>>>>> Hardware is a AMD phenom x6.
>>>>>>>> Below is the output of serial console of a failed boot.
>>>>>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>>>>>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>>>>>
>>>>>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>>>>>> must be related to something visible in the emulated view.
>>>>>>>
>>>>>>> Does this delta make any difference?
>>>>>> Yes it does, boots fine with this patch applied, thanks !
>>>>> That is bad though. :s
>>>>>
>>>>> It means that something in dom0 has an aversion to my attempt to lie
>>>>> less about the topology.
>>>>>
>>>>> Do you mind checking whether
>>>>>
>>>>> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>>>>>
>>>>> causes is to break again?
>>>> Used that in the is_hardware_domain() case and it boots fine.
>>> Hmm - curious. I am now even more confused.
>>>
>>> What about this?
>>>
>>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>>>
>>> It will leave the APIC_ID field zeroed rather than feeding v->vcpu_id
>>> back into it.
>> Also boots fine.
> Right. For my sanity, what about
>
> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
> res->b |= (v->vcpu_id * 2) << 24;
FWIW, I booted a 2-node
(XEN) CPU Vendor: AMD, Family 21 (0x15), Model 1 (0x1), Stepping 2
(raw 00600f12)
with Linux 4.10 and latest staging. (I thought perhaps my nightly missed
something because it's a single node)
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 19:15 ` Boris Ostrovsky
@ 2017-03-02 19:17 ` Andrew Cooper
2017-03-02 19:28 ` Sander Eikelenboom
2017-03-02 19:33 ` Boris Ostrovsky
0 siblings, 2 replies; 14+ messages in thread
From: Andrew Cooper @ 2017-03-02 19:17 UTC (permalink / raw)
To: Boris Ostrovsky, Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
On 02/03/17 19:15, Boris Ostrovsky wrote:
> On 03/02/2017 01:56 PM, Andrew Cooper wrote:
>> On 02/03/17 18:51, Sander Eikelenboom wrote:
>>> On 02/03/17 19:29, Andrew Cooper wrote:
>>>> On 02/03/17 18:25, Sander Eikelenboom wrote:
>>>>> On 02/03/17 18:38, Andrew Cooper wrote:
>>>>>> On 02/03/17 17:29, Sander Eikelenboom wrote:
>>>>>>> On 02/03/17 15:55, Andrew Cooper wrote:
>>>>>>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>>>>>>> Hi Andrew / Jan,
>>>>>>>>>
>>>>>>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>>>>>>> Bisection has turned up:
>>>>>>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>>>>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>>>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>>>>>>
>>>>>>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>>>>>>
>>>>>>>>> Hardware is a AMD phenom x6.
>>>>>>>>> Below is the output of serial console of a failed boot.
>>>>>>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>>>>>>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>>>>>>
>>>>>>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>>>>>>> must be related to something visible in the emulated view.
>>>>>>>>
>>>>>>>> Does this delta make any difference?
>>>>>>> Yes it does, boots fine with this patch applied, thanks !
>>>>>> That is bad though. :s
>>>>>>
>>>>>> It means that something in dom0 has an aversion to my attempt to lie
>>>>>> less about the topology.
>>>>>>
>>>>>> Do you mind checking whether
>>>>>>
>>>>>> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>>>>>>
>>>>>> causes is to break again?
>>>>> Used that in the is_hardware_domain() case and it boots fine.
>>>> Hmm - curious. I am now even more confused.
>>>>
>>>> What about this?
>>>>
>>>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>>>>
>>>> It will leave the APIC_ID field zeroed rather than feeding v->vcpu_id
>>>> back into it.
>>> Also boots fine.
>> Right. For my sanity, what about
>>
>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>> res->b |= (v->vcpu_id * 2) << 24;
> FWIW, I booted a 2-node
>
> (XEN) CPU Vendor: AMD, Family 21 (0x15), Model 1 (0x1), Stepping 2
> (raw 00600f12)
>
> with Linux 4.10 and latest staging. (I thought perhaps my nightly missed
> something because it's a single node)
I expect it might have something to do with fact that this failure to
boot is a 6-core system, rather than a power of two, at which point I
doubt the APIC IDs follow a linear trend.
(Properly fixing the reported topology is going to be a can of worms.
All this series is trying to do is use just enough duct-tape to get the
hypervisor into a state where we can sensibly fix the reported topology.)
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 19:17 ` Andrew Cooper
@ 2017-03-02 19:28 ` Sander Eikelenboom
2017-03-02 19:36 ` Andrew Cooper
2017-03-02 19:33 ` Boris Ostrovsky
1 sibling, 1 reply; 14+ messages in thread
From: Sander Eikelenboom @ 2017-03-02 19:28 UTC (permalink / raw)
To: Andrew Cooper, Boris Ostrovsky; +Cc: Jan Beulich, xen-devel
On 02/03/17 20:17, Andrew Cooper wrote:
> On 02/03/17 19:15, Boris Ostrovsky wrote:
>> On 03/02/2017 01:56 PM, Andrew Cooper wrote:
>>> On 02/03/17 18:51, Sander Eikelenboom wrote:
>>>> On 02/03/17 19:29, Andrew Cooper wrote:
>>>>> On 02/03/17 18:25, Sander Eikelenboom wrote:
>>>>>> On 02/03/17 18:38, Andrew Cooper wrote:
>>>>>>> On 02/03/17 17:29, Sander Eikelenboom wrote:
>>>>>>>> On 02/03/17 15:55, Andrew Cooper wrote:
>>>>>>>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>>>>>>>> Hi Andrew / Jan,
>>>>>>>>>>
>>>>>>>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>>>>>>>> Bisection has turned up:
>>>>>>>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>>>>>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>>>>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>>>>>>>
>>>>>>>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>>>>>>>
>>>>>>>>>> Hardware is a AMD phenom x6.
>>>>>>>>>> Below is the output of serial console of a failed boot.
>>>>>>>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>>>>>>>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>>>>>>>
>>>>>>>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>>>>>>>> must be related to something visible in the emulated view.
>>>>>>>>>
>>>>>>>>> Does this delta make any difference?
>>>>>>>> Yes it does, boots fine with this patch applied, thanks !
>>>>>>> That is bad though. :s
>>>>>>>
>>>>>>> It means that something in dom0 has an aversion to my attempt to lie
>>>>>>> less about the topology.
>>>>>>>
>>>>>>> Do you mind checking whether
>>>>>>>
>>>>>>> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>>>>>>>
>>>>>>> causes is to break again?
>>>>>> Used that in the is_hardware_domain() case and it boots fine.
>>>>> Hmm - curious. I am now even more confused.
>>>>>
>>>>> What about this?
>>>>>
>>>>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>>>>>
>>>>> It will leave the APIC_ID field zeroed rather than feeding v->vcpu_id
>>>>> back into it.
>>>> Also boots fine.
>>> Right. For my sanity, what about
>>>
>>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>>> res->b |= (v->vcpu_id * 2) << 24;
This doesn't boot.
--
Sander
>> FWIW, I booted a 2-node
>>
>> (XEN) CPU Vendor: AMD, Family 21 (0x15), Model 1 (0x1), Stepping 2
>> (raw 00600f12)
>>
>> with Linux 4.10 and latest staging. (I thought perhaps my nightly missed
>> something because it's a single node)
>
> I expect it might have something to do with fact that this failure to
> boot is a 6-core system, rather than a power of two, at which point I
> doubt the APIC IDs follow a linear trend.
>
> (Properly fixing the reported topology is going to be a can of worms.
> All this series is trying to do is use just enough duct-tape to get the
> hypervisor into a state where we can sensibly fix the reported topology.)
>
> ~Andrew
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 19:17 ` Andrew Cooper
2017-03-02 19:28 ` Sander Eikelenboom
@ 2017-03-02 19:33 ` Boris Ostrovsky
2017-03-02 20:02 ` Andrew Cooper
1 sibling, 1 reply; 14+ messages in thread
From: Boris Ostrovsky @ 2017-03-02 19:33 UTC (permalink / raw)
To: Andrew Cooper, Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
> I expect it might have something to do with fact that this failure to
> boot is a 6-core system, rather than a power of two, at which point I
> doubt the APIC IDs follow a linear trend.
>
> (Properly fixing the reported topology is going to be a can of worms.
> All this series is trying to do is use just enough duct-tape to get the
> hypervisor into a state where we can sensibly fix the reported topology.)
I think we are using the same duct-tape roll on the Linux side. For example,
cc272163ea55 ("x86/xen: Fix APIC id mismatch warning on Intel")
or
a6a198bc60e6 ("xen/x86: Update topology map for PV VCPUs")
and there are more.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 19:28 ` Sander Eikelenboom
@ 2017-03-02 19:36 ` Andrew Cooper
0 siblings, 0 replies; 14+ messages in thread
From: Andrew Cooper @ 2017-03-02 19:36 UTC (permalink / raw)
To: Sander Eikelenboom, Boris Ostrovsky; +Cc: Jan Beulich, xen-devel
On 02/03/17 19:28, Sander Eikelenboom wrote:
> On 02/03/17 20:17, Andrew Cooper wrote:
>> On 02/03/17 19:15, Boris Ostrovsky wrote:
>>> On 03/02/2017 01:56 PM, Andrew Cooper wrote:
>>>> On 02/03/17 18:51, Sander Eikelenboom wrote:
>>>>> On 02/03/17 19:29, Andrew Cooper wrote:
>>>>>> On 02/03/17 18:25, Sander Eikelenboom wrote:
>>>>>>> On 02/03/17 18:38, Andrew Cooper wrote:
>>>>>>>> On 02/03/17 17:29, Sander Eikelenboom wrote:
>>>>>>>>> On 02/03/17 15:55, Andrew Cooper wrote:
>>>>>>>>>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>>>>>>>>>> Hi Andrew / Jan,
>>>>>>>>>>>
>>>>>>>>>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot.
>>>>>>>>>>> Bisection has turned up:
>>>>>>>>>>> 5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>>>>>>>>> Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>>>>>>>>> Date: Fri Feb 17 17:10:50 2017 +0000
>>>>>>>>>>>
>>>>>>>>>>> x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>>>>>>>>>
>>>>>>>>>>> Hardware is a AMD phenom x6.
>>>>>>>>>>> Below is the output of serial console of a failed boot.
>>>>>>>>>> Hmm. Sorry for breaking this (although my AMD servers are booting fine).
>>>>>>>>> No problem, it is the staging branch of the unstable tree anyway ;-)
>>>>>>>>>
>>>>>>>>>> It is unfortunately not entirely obvious what Linux is objecting to, and
>>>>>>>>>> must be related to something visible in the emulated view.
>>>>>>>>>>
>>>>>>>>>> Does this delta make any difference?
>>>>>>>>> Yes it does, boots fine with this patch applied, thanks !
>>>>>>>> That is bad though. :s
>>>>>>>>
>>>>>>>> It means that something in dom0 has an aversion to my attempt to lie
>>>>>>>> less about the topology.
>>>>>>>>
>>>>>>>> Do you mind checking whether
>>>>>>>>
>>>>>>>> res->b = cpuid_ebx(0x1) & 0xff00ffffu;
>>>>>>>>
>>>>>>>> causes is to break again?
>>>>>>> Used that in the is_hardware_domain() case and it boots fine.
>>>>>> Hmm - curious. I am now even more confused.
>>>>>>
>>>>>> What about this?
>>>>>>
>>>>>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>>>>>>
>>>>>> It will leave the APIC_ID field zeroed rather than feeding v->vcpu_id
>>>>>> back into it.
>>>>> Also boots fine.
>>>> Right. For my sanity, what about
>>>>
>>>> res->b = cpuid_ebx(0x1) & 0x00ffffffu;
>>>> res->b |= (v->vcpu_id * 2) << 24;
> This doesn't boot.
> --
> Sander
Ok. So something in dom0 is taking extreme objection to the APIC IDs.
As a stopgap fix, this can be moved back to being HVM only. (And I am
going to have even more $FUN than I was originally planning, fixing the
topology reporting)
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
2017-03-02 19:33 ` Boris Ostrovsky
@ 2017-03-02 20:02 ` Andrew Cooper
0 siblings, 0 replies; 14+ messages in thread
From: Andrew Cooper @ 2017-03-02 20:02 UTC (permalink / raw)
To: Boris Ostrovsky, Sander Eikelenboom; +Cc: Jan Beulich, xen-devel
On 02/03/17 19:33, Boris Ostrovsky wrote:
>> I expect it might have something to do with fact that this failure to
>> boot is a 6-core system, rather than a power of two, at which point I
>> doubt the APIC IDs follow a linear trend.
>>
>> (Properly fixing the reported topology is going to be a can of worms.
>> All this series is trying to do is use just enough duct-tape to get the
>> hypervisor into a state where we can sensibly fix the reported topology.)
>
> I think we are using the same duct-tape roll on the Linux side.
Really? I'm sure I have used several rolls already ;p
> For example,
>
> cc272163ea55 ("x86/xen: Fix APIC id mismatch warning on Intel")
> or
> a6a198bc60e6 ("xen/x86: Update topology map for PV VCPUs")
>
> and there are more.
I seriously hope there is a compatible way to get the hypervisor side
correct without breaking the Linux-side, otherwise we are going to have
some hard decisions to make about which scenarios we can afford to regress.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2017-03-02 20:02 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-02 14:42 Xen-unstable: Bisected Host boot failure on AMD Phenom Sander Eikelenboom
2017-03-02 14:55 ` Andrew Cooper
2017-03-02 17:29 ` Sander Eikelenboom
2017-03-02 17:38 ` Andrew Cooper
2017-03-02 18:25 ` Sander Eikelenboom
2017-03-02 18:29 ` Andrew Cooper
2017-03-02 18:51 ` Sander Eikelenboom
2017-03-02 18:56 ` Andrew Cooper
2017-03-02 19:15 ` Boris Ostrovsky
2017-03-02 19:17 ` Andrew Cooper
2017-03-02 19:28 ` Sander Eikelenboom
2017-03-02 19:36 ` Andrew Cooper
2017-03-02 19:33 ` Boris Ostrovsky
2017-03-02 20:02 ` Andrew Cooper
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.