|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [BUG] (hvm)-virtualization doesn't work with xen 4.4
On Sat, May 10, 2014 at 08:18:32PM +0200, Fabio Fantoni wrote: > > Il 10/05/2014 19:47, Michael Mair-Keimberger ha scritto: > > On Sat, May 10, 2014 at 12:14:11PM +0200, Fabio Fantoni wrote: > >> Il 10/05/2014 12:08, Fabio Fantoni ha scritto: > >> > >> Il 10/05/2014 11:30, Michael Mair-Keimberger ha scritto: > >> > >> On Fri, May 09, 2014 at 07:43:18PM +0100, Andrew Cooper wrote: > >> > >> On 09/05/14 19:30, Michael Mair-Keimberger wrote: > >> > >> Hi Andrew, > >> Hi List, > >> > >> Sorry, for this late reply! > >> I didn't subscribe to the xen-devel mailing list and because of that i > >> didn't got any reply. On [1] it's written the lists policy is to CC > >> people so i though it's ok not to subscribe. It would be great if you > >> could CC me next time. > >> > >> [1] [1]http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen > >> > >> Because of that i've just copied your answer into a new mail and send it > >> directly to you + CC the list. Don't know if that is a proper way and i > >> hope i don't mess up to much... > >> > >> About my bug: > >> > >> > >> > >> Hi List, > >> > >> This is a forwarded mail which i already sent to the xen-users mailing > >> list, however it was suggested to open a BUG about my problem which > >> seems to work via the xen-devel mailing list. :) > >> > >> Below is my description about my problem - at the end i've added some > >> more information about my xen configuration. If you need some other > >> information, please let me know :) > >> > >> Can you please post the complete xl dmesg from boot including one > >> attempted boot of the VM. What you have pasted here is simply not > >> enough for us to help you with. If you could boot xen with "loglvl=all > >> guest_loglvl=all" on the command line, that would help things. > >> > >> Hmm, i though i did include a complete xl dmesg in my last mail (though > >> it > >> was a bit far back at mail), however, below is another xl dmesg. I've > >> also included my complete dmesg in case you need that too. > >> xl dmesg was done after i tried to start the vm via "xl create > >> /path/to/config" > >> > >> Can you do that with "loglvl=all guest_loglvl=all" on the Xen command > >> line please. It should produce a much larger log. > >> > >> Here we go :) > >> I did tried to start the vm a few times. > >> > >> Xen 4.4.0 > >> (XEN) Xen version 4.4.0 (@xonet.at) (x86_64-pc-linux-gnu-gcc (Gentoo > >> 4.8.2 p1.3r1, pie-0.5.8r1) 4.8.2) debug=n Sat May 10 09:46:31 CEST 2014 > >> (XEN) Latest ChangeSet: > >> (XEN) Bootloader: GRUB 2.02~beta1 > >> (XEN) Command line: dom0_mem=8192M,max:8192M iommu=debug,verbose xsave=1 > >> dom0_max_vcpus=4 dom0_vcpus_pin ivrs_ioapic[8]=00:14.0 loglvl=all > >> guest_loglvl=all > >> (XEN) Video information: > >> (XEN) VGA is text mode 80x25, font 8x16 > >> (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 - 000000000009f800 (usable) > >> (XEN) 000000000009f800 - 00000000000a0000 (reserved) > >> (XEN) 00000000000f0000 - 0000000000100000 (reserved) > >> (XEN) 0000000000100000 - 00000000bfda0000 (usable) > >> (XEN) 00000000bfda0000 - 00000000bfdd1000 (ACPI NVS) > >> (XEN) 00000000bfdd1000 - 00000000bfe00000 (ACPI data) > >> (XEN) 00000000bfe00000 - 00000000bff00000 (reserved) > >> (XEN) 00000000e0000000 - 00000000f0000000 (reserved) > >> (XEN) 00000000fec00000 - 0000000100000000 (reserved) > >> (XEN) 0000000100000000 - 000000043f000000 (usable) > >> (XEN) ACPI: RSDP 000F6BF0, 0014 (r0 GBT ) > >> (XEN) ACPI: RSDT BFDD1000, 0050 (r1 GBT GBTUACPI 42302E31 GBTU > >> 1010101) > >> (XEN) ACPI: FACP BFDD1080, 0074 (r1 GBT GBTUACPI 42302E31 GBTU > >> 1010101) > >> (XEN) ACPI: DSDT BFDD1100, 7997 (r1 GBT GBTUACPI 1000 MSFT > >> 3000000) > >> (XEN) ACPI: FACS BFDA0000, 0040 > >> (XEN) ACPI: MSDM BFDD8B80, 0055 (r3 GBT GBTUACPI 42302E31 GBTU > >> 1010101) > >> (XEN) ACPI: HPET BFDD8C00, 0038 (r1 GBT GBTUACPI 42302E31 GBTU > >> 98) > >> (XEN) ACPI: MCFG BFDD8C40, 003C (r1 GBT GBTUACPI 42302E31 GBTU > >> 1010101) > >> (XEN) ACPI: EUDS BFDD8CC0, 0740 (r1 GBT 0 > >> 0) > >> (XEN) ACPI: MATS BFDD9400, 0034 (r1 GBT 0 > >> 0) > >> (XEN) ACPI: TAMG BFDD9470, 0182 (r1 GBT GBT B0 5455312E BG.. > >> 53450101) > >> (XEN) ACPI: APIC BFDD8AC0, 00BC (r1 GBT GBTUACPI 42302E31 GBTU > >> 1010101) > >> (XEN) ACPI: MATS BFDD9600, 66BB (r1 MATS RCM 80000001 INTL > >> 20061109) > >> (XEN) ACPI: SSDT BFDDFD30, 1714 (r1 AMD POWERNOW 1 AMD > >> 1) > >> (XEN) ACPI: IVRS BFDE14C0, 0100 (r1 AMD RD890S 202031 AMD > >> 0) > >> (XEN) System RAM: 16365MB (16758012kB) > >> (XEN) No NUMA configuration found > >> (XEN) Faking a node at 0000000000000000-000000043f000000 > >> (XEN) Domain heap initialised > >> (XEN) found SMP MP-table at 000f4cd0 > >> (XEN) DMI 2.4 present. > >> (XEN) Using APIC driver default > >> (XEN) ACPI: PM-Timer IO Port: 0x808 > >> (XEN) ACPI: SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0] > >> (XEN) ACPI: wakeup_vec[bfda000c], vec_size[20] > >> (XEN) ACPI: Local APIC address 0xfee00000 > >> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > >> (XEN) Processor #0 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) > >> (XEN) Processor #1 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > >> (XEN) Processor #2 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) > >> (XEN) Processor #3 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled) > >> (XEN) Processor #4 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled) > >> (XEN) Processor #5 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled) > >> (XEN) Processor #6 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) > >> (XEN) Processor #7 5:2 APIC version 16 > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1]) > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1]) > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1]) > >> (XEN) ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1]) > >> (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) > >> (XEN) IOAPIC[0]: apic_id 8, version 33, address 0xfec00000, GSI 0-23 > >> (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 1 I/O APICs > >> (XEN) ACPI: HPET id: 0x10b9a201 base: 0xfed00000 > >> (XEN) ERST table was not found > >> (XEN) Using ACPI (MADT) for SMP configuration information > >> (XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs) > >> (XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X > >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > >> (XEN) Detected 4026.896 MHz processor. > >> (XEN) Initing memory sharing. > >> (XEN) xstate_init: using cntxt_size: 0x3c0 and states: 0x4000000000000007 > >> (XEN) AMD Fam15h machine check reporting enabled > >> (XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff > >> (XEN) PCI: MCFG area at e0000000 reserved in E820 > >> (XEN) PCI: Using MCFG for segment 0000 bus 00-ff > >> (XEN) AMD-Vi: Found MSI capability block at 0x54 > >> (XEN) AMD-Vi: ACPI Table: > >> (XEN) AMD-Vi: Signature IVRS > >> (XEN) AMD-Vi: Length 0x100 > >> (XEN) AMD-Vi: Revision 0x1 > >> (XEN) AMD-Vi: CheckSum 0x17 > >> (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 0x100 flags 0 > >> (XEN) AMD-Vi: Dev_Id Range: 0x100 -> 0x101 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x48 flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x200 flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x50 flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x300 flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x68 flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x400 flags 0 > >> (XEN) AMD-Vi: Dev_Id Range: 0x400 -> 0x401 > >> (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 0xa1 flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa2 flags 0 > >> (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 0x500 flags 0 > >> (XEN) AMD-Vi: Dev_Id Range: 0x500 -> 0x5ff 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 0x3 id 0x600 flags 0 > >> (XEN) AMD-Vi: Dev_Id Range: 0x600 -> 0x6ff > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa9 flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x700 flags 0 > >> (XEN) AMD-Vi: Dev_Id Range: 0x700 -> 0x7ff > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xaa flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x800 flags 0 > >> (XEN) AMD-Vi: Dev_Id Range: 0x800 -> 0x8ff > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xab flags 0 > >> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x900 flags 0 > >> (XEN) AMD-Vi: Dev_Id Range: 0x900 -> 0x9ff > >> (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 0x48 id 0 flags 0xd7 > >> (XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x1 handle 0x8 > >> (XEN) AMD-Vi: IVHD: Command line override present for IO-APIC 0x8(IVRS: > >> 0x8 devID 0000:00:14.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 0x8 > >> (XEN) AMD-Vi: IVHD: Command line override present for IO-APIC 0x8 > >> (XEN) AMD-Vi: IOMMU 0 Enabled. > >> (XEN) I/O virtualisation enabled > >> (XEN) - Dom0 mode: Relaxed > >> (XEN) Interrupt remapping enabled > >> (XEN) ENABLING IO-APIC IRQs > >> (XEN) -> Using new ACK method > >> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 > >> (XEN) Platform timer is 14.318MHz HPET > >> (XEN) Allocated console ring of 64 KiB. > >> (XEN) HVM: ASIDs enabled. > >> (XEN) SVM: Supported advanced features: > >> (XEN) - Nested Page Tables (NPT) > >> (XEN) - Last Branch Record (LBR) Virtualisation > >> (XEN) - Next-RIP Saved on #VMEXIT > >> (XEN) - VMCB Clean Bits > >> (XEN) - DecodeAssists > >> (XEN) - Pause-Intercept Filter > >> (XEN) - TSC Rate MSR > >> (XEN) HVM: SVM enabled > >> (XEN) HVM: Hardware Assisted Paging (HAP) detected > >> (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB > >> (XEN) HVM: PVH mode not supported on this platform > >> (XEN) spurious 8259A interrupt: IRQ7. > >> (XEN) CPU1: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) microcode: CPU1 collect_cpu_info: patch_id=0x600081c > >> (XEN) CPU2: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) microcode: CPU2 collect_cpu_info: patch_id=0x600081c > >> (XEN) CPU3: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) microcode: CPU3 collect_cpu_info: patch_id=0x600081c > >> (XEN) CPU4: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) microcode: CPU4 collect_cpu_info: patch_id=0x600081c > >> (XEN) CPU5: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) microcode: CPU5 collect_cpu_info: patch_id=0x600081c > >> (XEN) CPU6: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) microcode: CPU6 collect_cpu_info: patch_id=0x600081c > >> (XEN) Brought up 8 CPUs > >> (XEN) CPU7: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) microcode: CPU7 collect_cpu_info: patch_id=0x600081c > >> (XEN) ACPI sleep modes: S3 > >> (XEN) MCA: Use hw thresholding to adjust polling frequency > >> (XEN) mcheck_poll: Machine check polling timer started. > >> (XEN) *** LOADING DOMAIN 0 *** > >> (XEN) Xen kernel: 64-bit, lsb, compat32 > >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1bd5000 > >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >> (XEN) Dom0 alloc.: 000000042c000000->0000000430000000 (2080768 pages > >> to be allocated) > >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >> (XEN) Loaded kernel: ffffffff81000000->ffffffff81bd5000 > >> (XEN) Init. ramdisk: ffffffff81bd5000->ffffffff81bd5000 > >> (XEN) Phys-Mach map: ffffffff81bd5000->ffffffff82bd5000 > >> (XEN) Start info: ffffffff82bd5000->ffffffff82bd54b4 > >> (XEN) Page tables: ffffffff82bd6000->ffffffff82bf1000 > >> (XEN) Boot stack: ffffffff82bf1000->ffffffff82bf2000 > >> (XEN) TOTAL: ffffffff80000000->ffffffff83000000 > >> (XEN) ENTRY ADDRESS: ffffffff816701f0 > >> (XEN) Dom0 has maximum 4 VCPUs > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0, type = 0x6, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x2, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x10, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x48, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x50, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x68, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x88, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x90, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x92, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x98, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x9a, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa0, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa1, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa2, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa3, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa4, type = 0x5, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa5, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa8, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xa9, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xaa, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xab, type = 0x2, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xb0, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0xb2, type = 0x7, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Skipping host bridge 0000:00:18.0 > >> (XEN) AMD-Vi: Skipping host bridge 0000:00:18.1 > >> (XEN) AMD-Vi: Skipping host bridge 0000:00:18.2 > >> (XEN) AMD-Vi: Skipping host bridge 0000:00:18.3 > >> (XEN) AMD-Vi: Skipping host bridge 0000:00:18.4 > >> (XEN) AMD-Vi: Skipping host bridge 0000:00:18.5 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x100, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) ats.c:37: 0000:01:00.0: ATS capability found > >> (XEN) ats.c:79: 0000:01:00.0: ATS is enabled > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x101, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x200, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x300, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x400, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x401, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x600, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x700, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) AMD-Vi: Setup I/O page table: device id = 0x800, type = 0x1, root > >> table = 0x43238b000, domain = 0, paging mode = 3 > >> (XEN) Scrubbing Free RAM: > >> ................................................................................done. > >> (XEN) Initial low memory virq threshold set at 0x4000 pages. > >> (XEN) Std. Loglevel: All > >> (XEN) Guest Loglevel: All > >> (XEN) Xen is relinquishing VGA console. > >> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch > >> input to Xen) > >> (XEN) Freed 280kB init memory. > >> (XEN) traps.c:2514:d0 Domain attempted WRMSR 00000000c0010201 from > >> 0x0000000000000000 to 0x000000000000ffff. > >> (XEN) mm.c:809: d0: Forcing read-only access to MFN e0002 > >> (XEN) PCI add device 0000:00:00.0 > >> (XEN) PCI add device 0000:00:00.2 > >> (XEN) PCI add device 0000:00:02.0 > >> (XEN) PCI add device 0000:00:09.0 > >> (XEN) PCI add device 0000:00:0a.0 > >> (XEN) PCI add device 0000:00:0d.0 > >> (XEN) PCI add device 0000:00:11.0 > >> (XEN) PCI add device 0000:00:12.0 > >> (XEN) PCI add device 0000:00:12.2 > >> (XEN) PCI add device 0000:00:13.0 > >> (XEN) PCI add device 0000:00:13.2 > >> (XEN) PCI add device 0000:00:14.0 > >> (XEN) PCI add device 0000:00:14.1 > >> (XEN) PCI add device 0000:00:14.2 > >> (XEN) PCI add device 0000:00:14.3 > >> (XEN) PCI add device 0000:00:14.4 > >> (XEN) PCI add device 0000:00:14.5 > >> (XEN) PCI add device 0000:00:15.0 > >> (XEN) PCI add device 0000:00:15.1 > >> (XEN) PCI add device 0000:00:15.2 > >> (XEN) PCI add device 0000:00:15.3 > >> (XEN) PCI add device 0000:00:16.0 > >> (XEN) PCI add device 0000:00:16.2 > >> (XEN) PCI add device 0000:00:18.0 > >> (XEN) PCI add device 0000:00:18.1 > >> (XEN) PCI add device 0000:00:18.2 > >> (XEN) PCI add device 0000:00:18.3 > >> (XEN) PCI add device 0000:00:18.4 > >> (XEN) PCI add device 0000:00:18.5 > >> (XEN) PCI add device 0000:01:00.0 > >> (XEN) PCI add device 0000:01:00.1 > >> (XEN) PCI add device 0000:02:00.0 > >> (XEN) PCI add device 0000:03:00.0 > >> (XEN) PCI add device 0000:04:00.0 > >> (XEN) PCI add device 0000:04:00.1 > >> (XEN) PCI add device 0000:05:0e.0 > >> (XEN) PCI add device 0000:06:00.0 > >> (XEN) PCI add device 0000:07:00.0 > >> (XEN) PCI add device 0000:08:00.0 > >> (XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x2e332c > >> (d1) HVM Loader > >> (d1) Detected Xen v4.4.0 > >> (d1) Xenbus rings @0xfeffc000, event channel 4 > >> (d1) System requested SeaBIOS > >> (d1) CPU speed is 4027 MHz > >> (d1) Relocating guest memory for lowmem MMIO space disabled > >> (XEN) irq.c:270: Dom1 PCI link 0 changed 0 -> 5 > >> (d1) PCI-ISA link 0 routed to IRQ5 > >> (XEN) irq.c:270: Dom1 PCI link 1 changed 0 -> 10 > >> (d1) PCI-ISA link 1 routed to IRQ10 > >> (XEN) irq.c:270: Dom1 PCI link 2 changed 0 -> 11 > >> (d1) PCI-ISA link 2 routed to IRQ11 > >> (XEN) irq.c:270: Dom1 PCI link 3 changed 0 -> 5 > >> (d1) PCI-ISA link 3 routed to IRQ5 > >> (d1) pci dev 01:3 INTA->IRQ10 > >> (d1) pci dev 02:0 INTA->IRQ11 > >> (d1) No RAM in high memory; setting high_mem resource base to 100000000 > >> (d1) pci dev 03:0 bar 10 size 002000000: 0f0000008 > >> (d1) pci dev 02:0 bar 14 size 001000000: 0f2000008 > >> (d1) pci dev 03:0 bar 30 size 000010000: 0f3000000 > >> (d1) pci dev 03:0 bar 14 size 000001000: 0f3010000 > >> (d1) pci dev 02:0 bar 10 size 000000100: 00000c001 > >> (d1) pci dev 01:1 bar 20 size 000000010: 00000c101 > >> (d1) Multiprocessor initialisation: > >> (d1) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d1) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d1) Testing HVM environment: > >> (d1) - REP INSB across page boundaries ... passed > >> (d1) - GS base MSRs and SWAPGS ... passed > >> (d1) Passed 2 of 2 tests > >> (d1) Writing SMBIOS tables ... > >> (d1) Loading SeaBIOS ... > >> (d1) Creating MP tables ... > >> (d1) Loading ACPI ... > >> (d1) vm86 TSS at fc00a080 > >> (d1) BIOS map: > >> (d1) 10000-100d3: Scratch space > >> (d1) e0000-fffff: Main BIOS > >> (d1) E820 table: > >> (d1) [00]: 00000000:00000000 - 00000000:000a0000: RAM > >> (d1) HOLE: 00000000:000a0000 - 00000000:000e0000 > >> (d1) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED > >> (d1) [02]: 00000000:00100000 - 00000000:0f800000: RAM > >> (d1) HOLE: 00000000:0f800000 - 00000000:fc000000 > >> (d1) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > >> (d1) Invoking SeaBIOS ... > >> (XEN) io.c:204:d1 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 00 > >> 00 00 00 36 99 > >> (XEN) hvm.c:1346:d1 Triple fault on VCPU0 - invoking HVM shutdown action > >> 1. > >> (XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x2e3344 > >> (d2) HVM Loader > >> (d2) Detected Xen v4.4.0 > >> (d2) Xenbus rings @0xfeffc000, event channel 4 > >> (d2) System requested SeaBIOS > >> (d2) CPU speed is 4027 MHz > >> (d2) Relocating guest memory for lowmem MMIO space disabled > >> (XEN) irq.c:270: Dom2 PCI link 0 changed 0 -> 5 > >> (d2) PCI-ISA link 0 routed to IRQ5 > >> (XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10 > >> (d2) PCI-ISA link 1 routed to IRQ10 > >> (XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11 > >> (d2) PCI-ISA link 2 routed to IRQ11 > >> (XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5 > >> (d2) PCI-ISA link 3 routed to IRQ5 > >> (d2) pci dev 01:3 INTA->IRQ10 > >> (d2) pci dev 02:0 INTA->IRQ11 > >> (d2) No RAM in high memory; setting high_mem resource base to 100000000 > >> (d2) pci dev 03:0 bar 10 size 002000000: 0f0000008 > >> (d2) pci dev 02:0 bar 14 size 001000000: 0f2000008 > >> (d2) pci dev 03:0 bar 30 size 000010000: 0f3000000 > >> (d2) pci dev 03:0 bar 14 size 000001000: 0f3010000 > >> (d2) pci dev 02:0 bar 10 size 000000100: 00000c001 > >> (d2) pci dev 01:1 bar 20 size 000000010: 00000c101 > >> (d2) Multiprocessor initialisation: > >> (d2) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d2) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d2) Testing HVM environment: > >> (d2) - REP INSB across page boundaries ... passed > >> (d2) - GS base MSRs and SWAPGS ... passed > >> (d2) Passed 2 of 2 tests > >> (d2) Writing SMBIOS tables ... > >> (d2) Loading SeaBIOS ... > >> (d2) Creating MP tables ... > >> (d2) Loading ACPI ... > >> (d2) vm86 TSS at fc00a080 > >> (d2) BIOS map: > >> (d2) 10000-100d3: Scratch space > >> (d2) e0000-fffff: Main BIOS > >> (d2) E820 table: > >> (d2) [00]: 00000000:00000000 - 00000000:000a0000: RAM > >> (d2) HOLE: 00000000:000a0000 - 00000000:000e0000 > >> (d2) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED > >> (d2) [02]: 00000000:00100000 - 00000000:0f800000: RAM > >> (d2) HOLE: 00000000:0f800000 - 00000000:fc000000 > >> (d2) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > >> (d2) Invoking SeaBIOS ... > >> (XEN) io.c:204:d2 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 00 > >> 00 00 00 36 99 > >> (XEN) hvm.c:1346:d2 Triple fault on VCPU0 - invoking HVM shutdown action > >> 1. > >> (XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x2e5600 > >> (d3) HVM Loader > >> (d3) Detected Xen v4.4.0 > >> (d3) Xenbus rings @0xfeffc000, event channel 4 > >> (d3) System requested SeaBIOS > >> (d3) CPU speed is 4027 MHz > >> (d3) Relocating guest memory for lowmem MMIO space disabled > >> (XEN) irq.c:270: Dom3 PCI link 0 changed 0 -> 5 > >> (d3) PCI-ISA link 0 routed to IRQ5 > >> (XEN) irq.c:270: Dom3 PCI link 1 changed 0 -> 10 > >> (d3) PCI-ISA link 1 routed to IRQ10 > >> (XEN) irq.c:270: Dom3 PCI link 2 changed 0 -> 11 > >> (d3) PCI-ISA link 2 routed to IRQ11 > >> (XEN) irq.c:270: Dom3 PCI link 3 changed 0 -> 5 > >> (d3) PCI-ISA link 3 routed to IRQ5 > >> (d3) pci dev 01:3 INTA->IRQ10 > >> (d3) pci dev 02:0 INTA->IRQ11 > >> (d3) No RAM in high memory; setting high_mem resource base to 100000000 > >> (d3) pci dev 03:0 bar 10 size 002000000: 0f0000008 > >> (d3) pci dev 02:0 bar 14 size 001000000: 0f2000008 > >> (d3) pci dev 03:0 bar 30 size 000010000: 0f3000000 > >> (d3) pci dev 03:0 bar 14 size 000001000: 0f3010000 > >> (d3) pci dev 02:0 bar 10 size 000000100: 00000c001 > >> (d3) pci dev 01:1 bar 20 size 000000010: 00000c101 > >> (d3) Multiprocessor initialisation: > >> (d3) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d3) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d3) Testing HVM environment: > >> (d3) - REP INSB across page boundaries ... passed > >> (d3) - GS base MSRs and SWAPGS ... passed > >> (d3) Passed 2 of 2 tests > >> (d3) Writing SMBIOS tables ... > >> (d3) Loading SeaBIOS ... > >> (d3) Creating MP tables ... > >> (d3) Loading ACPI ... > >> (d3) vm86 TSS at fc00a080 > >> (d3) BIOS map: > >> (d3) 10000-100d3: Scratch space > >> (d3) e0000-fffff: Main BIOS > >> (d3) E820 table: > >> (d3) [00]: 00000000:00000000 - 00000000:000a0000: RAM > >> (d3) HOLE: 00000000:000a0000 - 00000000:000e0000 > >> (d3) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED > >> (d3) [02]: 00000000:00100000 - 00000000:0f800000: RAM > >> (d3) HOLE: 00000000:0f800000 - 00000000:fc000000 > >> (d3) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > >> (d3) Invoking SeaBIOS ... > >> (XEN) io.c:204:d3 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 00 > >> 00 00 00 36 99 > >> (XEN) hvm.c:1346:d3 Triple fault on VCPU0 - invoking HVM shutdown action > >> 1. > >> XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x2e1ec2 > >> (d7) HVM Loader > >> (d7) Detected Xen v4.4.0 > >> (d7) Xenbus rings @0xfeffc000, event channel 4 > >> (d7) System requested SeaBIOS > >> (d7) CPU speed is 4027 MHz > >> (d7) Relocating guest memory for lowmem MMIO space disabled > >> (XEN) irq.c:270: Dom7 PCI link 0 changed 0 -> 5 > >> (d7) PCI-ISA link 0 routed to IRQ5 > >> (XEN) irq.c:270: Dom7 PCI link 1 changed 0 -> 10 > >> (d7) PCI-ISA link 1 routed to IRQ10 > >> (XEN) irq.c:270: Dom7 PCI link 2 changed 0 -> 11 > >> (d7) PCI-ISA link 2 routed to IRQ11 > >> (XEN) irq.c:270: Dom7 PCI link 3 changed 0 -> 5 > >> (d7) PCI-ISA link 3 routed to IRQ5 > >> (d7) pci dev 01:3 INTA->IRQ10 > >> (d7) pci dev 02:0 INTA->IRQ11 > >> (d7) No RAM in high memory; setting high_mem resource base to 100000000 > >> (d7) pci dev 03:0 bar 10 size 002000000: 0f0000008 > >> (d7) pci dev 02:0 bar 14 size 001000000: 0f2000008 > >> (d7) pci dev 03:0 bar 30 size 000010000: 0f3000000 > >> (d7) pci dev 03:0 bar 14 size 000001000: 0f3010000 > >> (d7) pci dev 02:0 bar 10 size 000000100: 00000c001 > >> (d7) pci dev 01:1 bar 20 size 000000010: 00000c101 > >> (d7) Multiprocessor initialisation: > >> (d7) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d7) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d7) Testing HVM environment: > >> (d7) - REP INSB across page boundaries ... passed > >> (d7) - GS base MSRs and SWAPGS ... passed > >> (d7) Passed 2 of 2 tests > >> (d7) Writing SMBIOS tables ... > >> (d7) Loading SeaBIOS ... > >> (d7) Creating MP tables ... > >> (d7) Loading ACPI ... > >> (d7) vm86 TSS at fc00a080 > >> (d7) BIOS map: > >> (d7) 10000-100d3: Scratch space > >> (d7) e0000-fffff: Main BIOS > >> (d7) E820 table: > >> (d7) [00]: 00000000:00000000 - 00000000:000a0000: RAM > >> (d7) HOLE: 00000000:000a0000 - 00000000:000e0000 > >> (d7) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED > >> (d7) [02]: 00000000:00100000 - 00000000:0f800000: RAM > >> (d7) HOLE: 00000000:0f800000 - 00000000:fc000000 > >> (d7) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > >> (d7) Invoking SeaBIOS ... > >> (XEN) io.c:204:d7 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 00 > >> 00 00 00 36 99 > >> (XEN) hvm.c:1346:d7 Triple fault on VCPU0 - invoking HVM shutdown action > >> 1. > >> (XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x2e1ec6 > >> (d8) HVM Loader > >> (d8) Detected Xen v4.4.0 > >> (d8) Xenbus rings @0xfeffc000, event channel 4 > >> (d8) System requested SeaBIOS > >> (d8) CPU speed is 4027 MHz > >> (d8) Relocating guest memory for lowmem MMIO space disabled > >> (XEN) irq.c:270: Dom8 PCI link 0 changed 0 -> 5 > >> (d8) PCI-ISA link 0 routed to IRQ5 > >> (XEN) irq.c:270: Dom8 PCI link 1 changed 0 -> 10 > >> (d8) PCI-ISA link 1 routed to IRQ10 > >> (XEN) irq.c:270: Dom8 PCI link 2 changed 0 -> 11 > >> (d8) PCI-ISA link 2 routed to IRQ11 > >> (XEN) irq.c:270: Dom8 PCI link 3 changed 0 -> 5 > >> (d8) PCI-ISA link 3 routed to IRQ5 > >> (d8) pci dev 01:3 INTA->IRQ10 > >> (d8) pci dev 02:0 INTA->IRQ11 > >> (d8) No RAM in high memory; setting high_mem resource base to 100000000 > >> (d8) pci dev 03:0 bar 10 size 002000000: 0f0000008 > >> (d8) pci dev 02:0 bar 14 size 001000000: 0f2000008 > >> (d8) pci dev 03:0 bar 30 size 000010000: 0f3000000 > >> (d8) pci dev 03:0 bar 14 size 000001000: 0f3010000 > >> (d8) pci dev 02:0 bar 10 size 000000100: 00000c001 > >> (d8) pci dev 01:1 bar 20 size 000000010: 00000c101 > >> (d8) Multiprocessor initialisation: > >> (d8) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d8) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d8) Testing HVM environment: > >> (d8) - REP INSB across page boundaries ... passed > >> (d8) - GS base MSRs and SWAPGS ... passed > >> (d8) Passed 2 of 2 tests > >> (d8) Writing SMBIOS tables ... > >> (d8) Loading SeaBIOS ... > >> (d8) Creating MP tables ... > >> (d8) Loading ACPI ... > >> (d8) vm86 TSS at fc00a080 > >> (d8) BIOS map: > >> (d8) 10000-100d3: Scratch space > >> (d8) e0000-fffff: Main BIOS > >> (d8) E820 table: > >> (d8) [00]: 00000000:00000000 - 00000000:000a0000: RAM > >> (d8) HOLE: 00000000:000a0000 - 00000000:000e0000 > >> (d8) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED > >> (d8) [02]: 00000000:00100000 - 00000000:0f800000: RAM > >> (d8) HOLE: 00000000:0f800000 - 00000000:fc000000 > >> (d8) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > >> (d8) Invoking SeaBIOS ... > >> (XEN) io.c:204:d8 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 00 > >> 00 00 00 36 99 > >> (XEN) hvm.c:1346:d8 Triple fault on VCPU0 - invoking HVM shutdown action > >> 1. > >> (XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x2e5640 > >> (d9) HVM Loader > >> (d9) Detected Xen v4.4.0 > >> (d9) Xenbus rings @0xfeffc000, event channel 4 > >> (d9) System requested SeaBIOS > >> (d9) CPU speed is 4027 MHz > >> (d9) Relocating guest memory for lowmem MMIO space disabled > >> (XEN) irq.c:270: Dom9 PCI link 0 changed 0 -> 5 > >> (d9) PCI-ISA link 0 routed to IRQ5 > >> (XEN) irq.c:270: Dom9 PCI link 1 changed 0 -> 10 > >> (d9) PCI-ISA link 1 routed to IRQ10 > >> (XEN) irq.c:270: Dom9 PCI link 2 changed 0 -> 11 > >> (d9) PCI-ISA link 2 routed to IRQ11 > >> (XEN) irq.c:270: Dom9 PCI link 3 changed 0 -> 5 > >> (d9) PCI-ISA link 3 routed to IRQ5 > >> (d9) pci dev 01:3 INTA->IRQ10 > >> (d9) pci dev 02:0 INTA->IRQ11 > >> (d9) No RAM in high memory; setting high_mem resource base to 100000000 > >> (d9) pci dev 03:0 bar 10 size 002000000: 0f0000008 > >> (d9) pci dev 02:0 bar 14 size 001000000: 0f2000008 > >> (d9) pci dev 03:0 bar 30 size 000010000: 0f3000000 > >> (d9) pci dev 03:0 bar 14 size 000001000: 0f3010000 > >> (d9) pci dev 02:0 bar 10 size 000000100: 00000c001 > >> (d9) pci dev 01:1 bar 20 size 000000010: 00000c101 > >> (d9) Multiprocessor initialisation: > >> (d9) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d9) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d9) Testing HVM environment: > >> (d9) - REP INSB across page boundaries ... passed > >> (d9) - GS base MSRs and SWAPGS ... passed > >> (d9) Passed 2 of 2 tests > >> (d9) Writing SMBIOS tables ... > >> (d9) Loading SeaBIOS ... > >> (d9) Creating MP tables ... > >> (d9) Loading ACPI ... > >> (d9) vm86 TSS at fc00a080 > >> (d9) BIOS map: > >> (d9) 10000-100d3: Scratch space > >> (d9) e0000-fffff: Main BIOS > >> (d9) E820 table: > >> (d9) [00]: 00000000:00000000 - 00000000:000a0000: RAM > >> (d9) HOLE: 00000000:000a0000 - 00000000:000e0000 > >> (d9) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED > >> (d9) [02]: 00000000:00100000 - 00000000:0f800000: RAM > >> (d9) HOLE: 00000000:0f800000 - 00000000:fc000000 > >> (d9) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > >> (d9) Invoking SeaBIOS ... > >> (XEN) io.c:204:d9 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 00 > >> 00 00 00 36 99 > >> (XEN) hvm.c:1346:d9 Triple fault on VCPU0 - invoking HVM shutdown action > >> 1. > >> (XEN) AMD-Vi: Share p2m table with iommu: p2m table = 0x2f4865 > >> (d10) HVM Loader > >> (d10) Detected Xen v4.4.0 > >> (d10) Xenbus rings @0xfeffc000, event channel 4 > >> (d10) System requested SeaBIOS > >> (d10) CPU speed is 4027 MHz > >> (d10) Relocating guest memory for lowmem MMIO space disabled > >> (XEN) irq.c:270: Dom10 PCI link 0 changed 0 -> 5 > >> (d10) PCI-ISA link 0 routed to IRQ5 > >> (XEN) irq.c:270: Dom10 PCI link 1 changed 0 -> 10 > >> (d10) PCI-ISA link 1 routed to IRQ10 > >> (XEN) irq.c:270: Dom10 PCI link 2 changed 0 -> 11 > >> (d10) PCI-ISA link 2 routed to IRQ11 > >> (XEN) irq.c:270: Dom10 PCI link 3 changed 0 -> 5 > >> (d10) PCI-ISA link 3 routed to IRQ5 > >> (d10) pci dev 01:3 INTA->IRQ10 > >> (d10) pci dev 02:0 INTA->IRQ11 > >> (d10) No RAM in high memory; setting high_mem resource base to 100000000 > >> (d10) pci dev 03:0 bar 10 size 002000000: 0f0000008 > >> (d10) pci dev 02:0 bar 14 size 001000000: 0f2000008 > >> (d10) pci dev 03:0 bar 30 size 000010000: 0f3000000 > >> (d10) pci dev 03:0 bar 14 size 000001000: 0f3010000 > >> (d10) pci dev 02:0 bar 10 size 000000100: 00000c001 > >> (d10) pci dev 01:1 bar 20 size 000000010: 00000c101 > >> (d10) Multiprocessor initialisation: > >> (d10) - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d10) - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... > >> done. > >> (d10) Testing HVM environment: > >> (d10) - REP INSB across page boundaries ... passed > >> (d10) - GS base MSRs and SWAPGS ... passed > >> (d10) Passed 2 of 2 tests > >> (d10) Writing SMBIOS tables ... > >> (d10) Loading SeaBIOS ... > >> (d10) Creating MP tables ... > >> (d10) Loading ACPI ... > >> (d10) vm86 TSS at fc00a080 > >> (d10) BIOS map: > >> (d10) 10000-100d3: Scratch space > >> (d10) e0000-fffff: Main BIOS > >> (d10) E820 table: > >> (d10) [00]: 00000000:00000000 - 00000000:000a0000: RAM > >> (d10) HOLE: 00000000:000a0000 - 00000000:000e0000 > >> (d10) [01]: 00000000:000e0000 - 00000000:00100000: RESERVED > >> (d10) [02]: 00000000:00100000 - 00000000:0f800000: RAM > >> (d10) HOLE: 00000000:0f800000 - 00000000:fc000000 > >> (d10) [03]: 00000000:fc000000 - 00000001:00000000: RESERVED > >> (d10) Invoking SeaBIOS ... > >> (XEN) io.c:204:d10 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 00 > >> 00 00 00 36 99 > >> (XEN) hvm.c:1346:d10 Triple fault on VCPU0 - invoking HVM shutdown > >> action 1. > >> > >> What seabios and qemu versions your are using? > >> Xen (also unstable) not use the latest seabios and qemu versions for > >> now, if you build from xen source for update seabios and/or qemu you > >> must change the repositories urls and revisions. > >> You can also use more updated versions from distro package, set them > >> in > >> xen's configure. > >> Another important note is that update seabios package not update it > >> in > >> xen's hvmloader but need to be recompiled (xen or at least hvmloader) > >> Here a bugreport with same error that can help you: > >> [2]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737905 > >> > >> Sorry for my bad english. > > > > Seabios version: seabios-1.7.3.2 > > Qemu version: QEMU emulator version 2.0.0 > > > > Note: Qemu is included in xen, i don't usually use system qemu. (System > > qemu is also at version 2.0.0 which also didn't worked when i tried it.) > > > > From the bug report it seems seabios 1.7.4 is affected by this problem. > > I couldn't find out if previous versions are affected too, but since > > gentoo doesn't even provide 1.7.4 yet and xen should use system's > > seabios (via the --with-system-seabios=/path/to/seabios switch) i > > shouldn't hit this problem, should i? > > Rebuilding anything isn't a problem at all (gentoo builds everything > > from source by default) so i could try out a older version of seabios. > > Is there any particular version which shouldn't be affected? > > > > Thanks for the help. > > There were no build xen 1.7.4 with seabios then what reported the bug > even if you installed the updated package seabios still had seabios old > in hvmloader. > I'm also open a discussion about this problem: > http://lists.xen.org/archives/html/xen-devel/2014-05/msg01338.html > > I'm using qemu 2.0 since rc0, I haven't my testing system here but if I > remember good I'm using on it seabios package 1.7.4-4 (compiled from > debian unstable source 1-2 months ago) and I never had bios problems for > now, try to update seabios. > If you not have distro package updated change seabios url and revision > in xen and remove "--with-system-seabios" for now. > In Config.mk change: > SEABIOS_UPSTREAM_URL ?= git://git.qemu.org/seabios.git > SEABIOS_UPSTREAM_TAG ?= rel-1.7.4 > Is a long time I not use this change but if I remember good should be > correct. > > If the seabios will not solves the problem post other details, for > example the exact xen and qemu commit used (and additional patches > added), the domU's xl cfg, xl -vvv create output, domU's qemu log ecc... That was it :) I've created my own seabios-1.7.4 ebuild and build xen against it. hvm virtualization works again now. Many thanks! Now i only have to get pci passthrough work again, but i guess i gonna write another mail about that :) > > > > >> Readded initial sender to recipient, sorry, seems that thunderbird's > >> replies to all didn't include him. > >> > >> > >> Xen 4.4.0 > >> (XEN) Xen version 4.4.0 (@xonet.at) (x86_64-pc-linux-gnu-gcc (Gentoo > >> > >> 4.8.2 p1.3r1, pie-0.5.8r1) 4.8.2) debug=n Sat Apr 12 09:46:34 CEST 2014 > >> > >> (XEN) Latest ChangeSet: > >> (XEN) Bootloader: GRUB 2.02~beta1 > >> (XEN) Command line: dom0_mem=8192M,max:8192M iommu=debug,verbose > >> > >> xsave=1 dom0_max_vcpus=4 dom0_vcpus_pin ivrs_ioapic[8]=00:14.0 > >> > >> (XEN) Video information: > >> (XEN) VGA is text mode 80x25, font 8x16 > >> (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 - 000000000009f800 (usable) > >> (XEN) 000000000009f800 - 00000000000a0000 (reserved) > >> (XEN) 00000000000f0000 - 0000000000100000 (reserved) > >> (XEN) 0000000000100000 - 00000000bfda0000 (usable) > >> (XEN) 00000000bfda0000 - 00000000bfdd1000 (ACPI NVS) > >> (XEN) 00000000bfdd1000 - 00000000bfe00000 (ACPI data) > >> (XEN) 00000000bfe00000 - 00000000bff00000 (reserved) > >> (XEN) 00000000e0000000 - 00000000f0000000 (reserved) > >> (XEN) 00000000fec00000 - 0000000100000000 (reserved) > >> (XEN) 0000000100000000 - 000000043f000000 (usable) > >> (XEN) ACPI: RSDP 000F6BF0, 0014 (r0 GBT ) > >> (XEN) ACPI: RSDT BFDD1000, 0050 (r1 GBT GBTUACPI 42302E31 GBTU > >> > >> 1010101) > >> > >> (XEN) ACPI: FACP BFDD1080, 0074 (r1 GBT GBTUACPI 42302E31 GBTU > >> > >> 1010101) > >> > >> (XEN) ACPI: DSDT BFDD1100, 7997 (r1 GBT GBTUACPI 1000 MSFT > >> > >> 3000000) > >> > >> (XEN) ACPI: FACS BFDA0000, 0040 > >> (XEN) ACPI: MSDM BFDD8B80, 0055 (r3 GBT GBTUACPI 42302E31 GBTU > >> > >> 1010101) > >> > >> (XEN) ACPI: HPET BFDD8C00, 0038 (r1 GBT GBTUACPI 42302E31 > >> > >> GBTU 98) > >> > >> (XEN) ACPI: MCFG BFDD8C40, 003C (r1 GBT GBTUACPI 42302E31 GBTU > >> > >> 1010101) > >> > >> (XEN) ACPI: EUDS BFDD8CC0, 0740 (r1 GBT > >> > >> 0 0) > >> > >> (XEN) ACPI: MATS BFDD9400, 0034 (r1 GBT > >> > >> 0 0) > >> > >> (XEN) ACPI: TAMG BFDD9470, 0182 (r1 GBT GBT B0 5455312E BG.. > >> > >> 53450101) > >> > >> (XEN) ACPI: APIC BFDD8AC0, 00BC (r1 GBT GBTUACPI 42302E31 GBTU > >> > >> 1010101) > >> > >> (XEN) ACPI: MATS BFDD9600, 66BB (r1 MATS RCM 80000001 INTL > >> > >> 20061109) > >> > >> (XEN) ACPI: SSDT BFDDFD30, 1714 (r1 AMD POWERNOW 1 > >> > >> AMD 1) > >> > >> (XEN) ACPI: IVRS BFDE14C0, 0100 (r1 AMD RD890S 202031 > >> > >> AMD 0) > >> > >> (XEN) System RAM: 16365MB (16758012kB) > >> (XEN) Domain heap initialised > >> (XEN) Processor #0 5:2 APIC version 16 > >> (XEN) Processor #1 5:2 APIC version 16 > >> (XEN) Processor #2 5:2 APIC version 16 > >> (XEN) Processor #3 5:2 APIC version 16 > >> (XEN) Processor #4 5:2 APIC version 16 > >> (XEN) Processor #5 5:2 APIC version 16 > >> (XEN) Processor #6 5:2 APIC version 16 > >> (XEN) Processor #7 5:2 APIC version 16 > >> (XEN) IOAPIC[0]: apic_id 8, version 33, address 0xfec00000, GSI 0-23 > >> (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > >> (XEN) Using scheduler: SMP Credit Scheduler (credit) > >> (XEN) Detected 4026.919 MHz processor. > >> (XEN) Initing memory sharing. > >> (XEN) xstate_init: using cntxt_size: 0x3c0 and states: 0x4000000000000007 > >> (XEN) AMD-Vi: IOMMU 0 Enabled. > >> (XEN) I/O virtualisation enabled > >> (XEN) - Dom0 mode: Relaxed > >> (XEN) Interrupt remapping enabled > >> (XEN) ENABLING IO-APIC IRQs > >> (XEN) -> Using new ACK method > >> (XEN) Platform timer is 14.318MHz HPET > >> (XEN) Allocated console ring of 16 KiB. > >> (XEN) HVM: ASIDs enabled. > >> (XEN) SVM: Supported advanced features: > >> (XEN) - Nested Page Tables (NPT) > >> (XEN) - Last Branch Record (LBR) Virtualisation > >> (XEN) - Next-RIP Saved on #VMEXIT > >> (XEN) - VMCB Clean Bits > >> (XEN) - DecodeAssists > >> (XEN) - Pause-Intercept Filter > >> (XEN) - TSC Rate MSR > >> (XEN) HVM: SVM enabled > >> (XEN) HVM: Hardware Assisted Paging (HAP) detected > >> (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB > >> (XEN) spurious 8259A interrupt: IRQ7. > >> (XEN) CPU1: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) CPU2: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) CPU3: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) CPU4: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) CPU5: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) CPU6: No irq handler for vector e7 (IRQ -2147483648) > >> (XEN) Brought up 8 CPUs > >> (XEN) CPU7: No irq handler for vector e7 (IRQ -2147483648) > >> > >> Certainly unrelated to your bug, but this would indicate some early > >> synchronisation issue between booting APs and inheriting global irq > >> state. > >> > >> Probably yes - i got those messages before too and never had problems. > >> > >> (XEN) *** LOADING DOMAIN 0 *** > >> (XEN) Xen kernel: 64-bit, lsb, compat32 > >> (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1bd5000 > >> (XEN) PHYSICAL MEMORY ARRANGEMENT: > >> (XEN) Dom0 alloc.: 000000042c000000->0000000430000000 (2080768 > >> > >> pages to be allocated) > >> > >> (XEN) VIRTUAL MEMORY ARRANGEMENT: > >> (XEN) Loaded kernel: ffffffff81000000->ffffffff81bd5000 > >> (XEN) Init. ramdisk: ffffffff81bd5000->ffffffff81bd5000 > >> (XEN) Phys-Mach map: ffffffff81bd5000->ffffffff82bd5000 > >> (XEN) Start info: ffffffff82bd5000->ffffffff82bd54b4 > >> (XEN) Page tables: ffffffff82bd6000->ffffffff82bf1000 > >> (XEN) Boot stack: ffffffff82bf1000->ffffffff82bf2000 > >> (XEN) TOTAL: ffffffff80000000->ffffffff83000000 > >> (XEN) ENTRY ADDRESS: ffffffff816701f0 > >> (XEN) Dom0 has maximum 4 VCPUs > >> (XEN) Scrubbing Free RAM: > >> > >> > >> ................................................................................done. > >> > >> (XEN) Initial low memory virq threshold set at 0x4000 pages. > >> (XEN) Std. Loglevel: Errors and warnings > >> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > >> (XEN) Xen is relinquishing VGA console. > >> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch > >> > >> input to Xen) > >> > >> (XEN) Freed 280kB init memory. > >> (XEN) traps.c:2514:d0 Domain attempted WRMSR 00000000c0010201 from > >> > >> 0x0000000000000000 to 0x000000000000ffff. > >> > >> (XEN) mm.c:809: d0: Forcing read-only access to MFN e0002 > >> > >> This is curious, but probably unrelated to your bug. > >> > >> Same again. I had this message before as well. > >> > >> If you want we can go look into those messages too, i'm happy to help > >> you guys with making xen better :) > >> > >> > >> (XEN) io.c:204:d2 MMIO emulation failed @ 0008:ffff1f50: 32 00 00 00 > >> > >> 00 00 00 00 36 99 > >> > >> Right, so this is a different instruction this time, and is 'xor > >> (%{r,e}ax),%al' this time, which could plausibly hit emulation if > >> %{r,e}ax is a bad pointer. > >> > >> If you try to boot the guest several times, how does this particular > >> line change? > >> > >> It doesn't change at all. As you can see in the xl dmesg output before, > >> i've tried to boot the guest several times and always had the same > >> output. > >> However, the line changes if i start xen without any command line > >> arguments. I've added you another xl dmesg without any command line > >> arguments except "loglvl=all guest_loglvl=all". The particular line > >> however looks in such case like following: > >> > >> (XEN) io.c:204:d1 MMIO emulation failed @ 0008:ffff1f50: 4a 00 00 00 00 > >> 00 00 00 36 99 > >> > >> > >> Can you set on_crash="preserve" for the vm, then also attach the result > >> of `xen-hvmctx $DOMID` > >> > >> Sadly that doesn't work. It seems the vm already gets killed before xen > >> could preserve anything. > >> > >> Output from /var/log/xen/xl-HVM_domU.log > >> > >> Waiting for domain HVM_domU (domid 10) to die [pid 3503] > >> Domain 10 has shut down, reason code 1 0x1 > >> Action for shutdown reason code 1 is destroy > >> Domain 10 needs to be cleaned up: destroying the domain > >> Done. Exiting now > >> > >> If i try do use domain 10 i've got following: > >> > >> # xen-hvmctx 10 > >> Error: can't get record length for dom 10 > >> > >> > >> Thanks, > >> > >> ~Andrew > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> [3]Xen-devel@xxxxxxxxxxxxx > >> [4]http://lists.xen.org/xen-devel > >> > >> References > >> > >> Visible links > >> 1. http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen > >> 2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737905 > >> 3. mailto:Xen-devel@xxxxxxxxxxxxx > >> 4. http://lists.xen.org/xen-devel > >> > >> > >> ELinks: No such file or directory > -- greetings Michael Mair-Keimberger Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |