This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Vt-d not working with 3.4.1

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Vt-d not working with 3.4.1
From: "Bonenkamp, Ralf" <ralf.bonenkamp@xxxxxxxx>
Date: Mon, 10 Aug 2009 22:14:20 +0200
Delivery-date: Mon, 17 Aug 2009 06:59:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoYccHBg0fqPQ1rQoK+sC8PO115tQBhTntA
Thread-topic: Vt-d not working with 3.4.1
Hi folks,

currently I try to setup a new xen host v3.4.1 on top of a Asus P5E-VM
DO (latest BIOS, Vt-d capable and enabled in BIOS) to migrate my
extisting HVMs (Win2k3 server) running on Xen v3.3.0 to a new home. I
want to switch over to 3.4.1 to (hopefully!) passthrough my ISDN board
to a HVM domU.
Unfortunate there seem some issue with the VT-d DMAR tables which is
beyond my knowledge and probably someone has some hint how to proceed?

Find attached the output of xm dmesg. Please drop a short note whatever
additional information might be needed... 

Best regards & thanks in advance
Ralf Bonenkamp

---- snip
__  __            _____ _  _    _
 \ \/ /___ _ __   |___ /| || |  / |
  \  // _ \ '_ \    |_ \| || |_ | |
  /  \  __/ | | |  ___) |__   _|| |
 /_/\_\___|_| |_| |____(_) |_|(_)_|

(XEN) Xen version 3.4.1 (root@xxxxxxxxxxxxx) (gcc version 4.3.3 (Ubuntu
4.3.3-5ubuntu4) ) Sat Aug  8 21:53:36 BST 2009
(XEN) Latest ChangeSet: Thu Aug 06 13:27:53 2009 +0100
(XEN) Command line: iommu_inclusive_mapping=1 iommu=1
(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 0 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007d550000 (usable)
(XEN)  000000007d550000 - 000000007d55e000 (ACPI data)
(XEN)  000000007d55e000 - 000000007d5e0000 (ACPI NVS)
(XEN)  000000007d5e0000 - 000000007d600000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffc00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2004MB (2053048kB)
(XEN) ACPI: RSDP 000F9A80, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT 7D550100, 0064 (r1 A_M_I_ OEMXSDT   2000917 MSFT
(XEN) ACPI: FACP 7D550290, 00F4 (r3 A_M_I_ OEMFACP   2000917 MSFT
(XEN) ACPI: DSDT 7D5505C0, 843B (r1  A0869 A0869001        1 INTL
(XEN) ACPI: FACS 7D55E000, 0040
(XEN) ACPI: APIC 7D550390, 006C (r1 A_M_I_ OEMAPIC   2000917 MSFT
(XEN) ACPI: MCFG 7D550400, 003C (r1 A_M_I_ OEMMCFG   2000917 MSFT
(XEN) ACPI: OEMB 7D55E040, 0081 (r1 A_M_I_ AMI_OEM   2000917 MSFT
(XEN) ACPI: HPET 7D558A00, 0038 (r1 A_M_I_ OEMHPET   2000917 MSFT
(XEN) ACPI: GSCI 7D55E0D0, 2024 (r1 A_M_I_ GMCHSCI   2000917 MSFT
(XEN) ACPI: iEIT 7D560100, 00B0 (r1 A_M_I_ EITTABLE  2000917 MSFT
(XEN) ACPI: DMAR 7D5601B0, 0158 (r1    AMI  OEMDMAR        1 MSFT
(XEN) Domain heap initialised
(XEN) Processor #0 7:7 APIC version 20
(XEN) Processor #1 7:7 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) [VT-D]dmar.c:401: RMRR address range not in reserved memory base =
7d600000 end = 7dffffff; iommu_inclusive_mapping=1 parameter may be
(XEN) Intel VT-d DMAR tables have been parsed.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2999.981 MHz processor.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz stepping 0a
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz stepping 0a
(XEN) Total of 2 processors activated.
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) Intel VT-d Snoop Control not supported.
(XEN) Intel VT-d DMA Passthrough not supported.
(XEN) Intel VT-d Queued Invalidation not supported.
(XEN) Intel VT-d Interrupt Remapping not supported.
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:691: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:676: iommu_fault:DMA Write: 0:2.0 addr 400000000
REASON 5 iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: iommu = ffff83007d54a370 bdf = 0:2:0 gmfn =
(XEN)     root_entry = ffff83007d543000
(XEN)     root_entry[0] = 795c6001
(XEN)     context = ffff8300795c6000
(XEN)     context[10] = 101_7d0ec001
(XEN)     l3 = ffff83007d0ec000
(XEN)     l3_index = 10
(XEN)     l3[10] = 0
(XEN)     l3[10] not present
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x76d000
(XEN)  Dom0 alloc.:   0000000076000000->0000000078000000 (465255 pages
to be allocated)
(XEN)  Loaded kernel: ffffffff80200000->ffffffff8076d000
(XEN)  Init. ramdisk: ffffffff8076d000->ffffffff81d4c600
(XEN)  Phys-Mach map: ffffe20000000000->ffffe2000039cb38
(XEN)  Start info:    ffffffff81d4d000->ffffffff81d4d4b4
(XEN)  Page tables:   ffffffff81d4e000->ffffffff81d61000
(XEN)  Boot stack:    ffffffff81d61000->ffffffff81d62000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82000000
(XEN)  ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(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 132kB init memory.
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 0 initialization completed
(XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space
(XEN) CPU 1 initialization completed
(XEN) no cpu_id for acpi_id 3
(XEN) no cpu_id for acpi_id 4

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Vt-d not working with 3.4.1, Bonenkamp, Ralf <=