[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Unable to boot Xen 4.8 with iommu=0



Hi all,
I'm having some strange issues with Xen 4.8 when I try to boot with
iommu disabled.

(XEN) Xen version 4.8.0 (root@lan) (gcc (Debian 5.4.1-4) 5.4.1
20161202) debug=n  Tue Feb 14 15:32:55 MST 2017
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.02~beta3-4
(XEN) Command line: placeholder dom0_mem=4096M,max:4096M
dom0_max_vcpus=4 dom0_vcpus_pin=true hap_1gb=false hap_2mb=false
altp2m=1 com1=115200,8n1,amt loglvl=all guest_loglvl=all console=com1
flask_enforcing=1 iommu=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 - 000000000008f000 (usable)
(XEN)  000000000008f000 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000020000000 (usable)
(XEN)  0000000020000000 - 0000000020200000 (reserved)
(XEN)  0000000020200000 - 0000000040000000 (usable)
(XEN)  0000000040000000 - 0000000040200000 (reserved)
(XEN)  0000000040200000 - 000000007a556000 (usable)
(XEN)  000000007a556000 - 000000007a5a5000 (ACPI NVS)
(XEN)  000000007a5a5000 - 000000007a5ae000 (ACPI data)
(XEN)  000000007a5ae000 - 000000007a6a1000 (reserved)
(XEN)  000000007a6a1000 - 000000007a6a3000 (usable)
(XEN)  000000007a6a3000 - 000000007a8c2000 (reserved)
(XEN)  000000007a8c2000 - 000000007a8c3000 (usable)
(XEN)  000000007a8c3000 - 000000007a8d3000 (reserved)
(XEN)  000000007a8d3000 - 000000007a8f1000 (ACPI NVS)
(XEN)  000000007a8f1000 - 000000007a915000 (reserved)
(XEN)  000000007a915000 - 000000007a958000 (ACPI NVS)
(XEN)  000000007a958000 - 000000007ab78000 (reserved)
(XEN)  000000007ab78000 - 000000007ad00000 (usable)
(XEN)  000000007ad00000 - 000000007b000000 (reserved)
(XEN)  000000007b800000 - 000000007fa00000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed40000 (reserved)
(XEN)  00000000ff000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000047e600000 (usable)
(XEN) ACPI: RSDP 000F0450, 0024 (r2  INTEL)
(XEN) ACPI: XSDT 7A5A5070, 0064 (r1 INTEL  DQ67SW    1072009 AMI     10013)
(XEN) ACPI: FACP 7A5ACB50, 00F4 (r4 INTEL  DQ67SW    1072009 AMI     10013)
(XEN) ACPI: DSDT 7A5A5168, 79E1 (r2 INTEL  DQ67SW         16 INTL 20051117)
(XEN) ACPI: FACS 7A8D7F80, 0040
(XEN) ACPI: APIC 7A5ACC48, 0092 (r3 INTEL  DQ67SW    1072009 AMI     10013)
(XEN) ACPI: TCPA 7A5ACCE0, 0032 (r2 INTEL  DQ67SW          1 MSFT  1000013)
(XEN) ACPI: SSDT 7A5ACD18, 01D6 (r1 INTEL  DQ67SW          1 MSFT  3000001)
(XEN) ACPI: MCFG 7A5ACEF0, 003C (r1 INTEL  DQ67SW    1072009 MSFT       97)
(XEN) ACPI: HPET 7A5ACF30, 0038 (r1 INTEL  DQ67SW    1072009 AMI.        4)
(XEN) ACPI: ASF! 7A5ACF68, 00A0 (r32 INTEL  DQ67SW          1 TFSM    F4240)
(XEN) ACPI: DMAR 7A5AD008, 00E8 (r1 INTEL  DQ67SW          1 INTL        1)
(XEN) System RAM: 16264MB (16654784kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-000000047e600000
(XEN) Domain heap initialised
(XEN) CPU Vendor: Intel, Family 6 (0x6), Model 42 (0x2a), Stepping 7
(raw 000206a7)
(XEN) found SMP MP-table at 000fda00
(XEN) DMI 2.6 present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0x408 (32 bits)
(XEN) ACPI: SLEEP INFO: pm1x_cnt[1:404,1:0], pm1x_evt[1:400,1:0]
(XEN) ACPI: 32/64X FACS address mismatch in FADT -
7a8d7f80/0000000000000000, using 32
(XEN) ACPI:             wakeup_vec[7a8d7f8c], 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[0x02] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, 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 high 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: 0x8086a701 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) Switched to APIC driver x2apic_cluster.
(XEN) XSM Framework v1.0.0 initialized
(XEN) Flask: 128 avtab hash slots, 394 rules.
(XEN) Flask: 128 avtab hash slots, 394 rules.
(XEN) Flask:  5 users, 3 roles, 43 types, 2 bools
(XEN) Flask:  12 classes, 394 rules
(XEN) Flask:  Starting in enforcing mode.
(XEN) xstate: size: 0x340 and states: 0x7
(XEN) Intel machine check reporting enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 3392.326 MHz processor.
(XEN) Initing memory sharing.
(XEN) alt table ffff82d0802d3f38 -> ffff82d0802d5564
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - 3f
(XEN) PCI: Not using MCFG for segment 0000 bus 00-3f
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Couldn't enable IOMMU and iommu=required/force
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

As seen in the command line iommu is not set to required or forced.
Yet Xen thinks it is set to required/force. Has anyone else run into
this issue?

Tamas

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.