Mark Hurenkamp
2010-Mar-30 20:57 UTC
[Xen-devel] VT-d on Asus P7P55D-Evo: IOMMU not supported
Hi,
Having updated my Xen to 4.0-rc9-pre recently, i decided to try
booting without the iommu=0 flag.
The system doesn''t crash now (which is an improvement), but gracefully
disables VT-d due to an
unsupported IOMMU.
I''ve attached the output of xm dmesg, hope it is of use to someone.
Do let me know if there''s something more i can do to help in getting
VT-d working on this board.
Regards,
Mark.
__ __ _ _ ___ ___ ___
\ \/ /___ _ __ | || | / _ \ / _ \ _ __ ___ / _ \ _ __ _ __
___
\ // _ \ ''_ \ | || |_| | | | | | |__| ''__/ __| (_) |__|
''_ \|
''__/ _ \
/ \ __/ | | | |__ _| |_| | |_| |__| | | (__ \__, |__| |_) | |
| __/
/_/\_\___|_| |_| |_|(_)___(_)___/ |_| \___| /_/ | .__/|_|
\___|
|_|
(XEN) Xen version 4.0.0-rc9-pre (root@karpeer.net) (gcc version 4.4.1
(Ubuntu 4.4.1-4ubuntu9) ) Mon Mar 29 23:07:18 CEST 2010
(XEN) Latest ChangeSet: Sat Mar 27 16:01:35 2010 +0000
21078:f3db0ae08304
(XEN) Command line:
(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 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007f670000 (usable)
(XEN) 000000007f670000 - 000000007f688000 (ACPI data)
(XEN) 000000007f688000 - 000000007f6dc000 (ACPI NVS)
(XEN) 000000007f6dc000 - 000000007f700000 (reserved)
(XEN) 000000007f800000 - 0000000080000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000180000000 (usable)
(XEN) ACPI: RSDP 000FB470, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT 7F670100, 0064 (r1 022210 XSDT2250 20100222
MSFT 97)
(XEN) ACPI: FACP 7F670290, 00F4 (r3 022210 FACP2250 20100222
MSFT 97)
(XEN) ACPI: DSDT 7F6704A0, EF5B (r1 A1290 A1290001 1 INTL
20060113)
(XEN) ACPI: FACS 7F688000, 0040
(XEN) ACPI: APIC 7F670390, 00CC (r1 022210 APIC2250 20100222
MSFT 97)
(XEN) ACPI: MCFG 7F670460, 003C (r1 022210 OEMMCFG 20100222
MSFT 97)
(XEN) ACPI: OEMB 7F688040, 0072 (r1 022210 OEMB2250 20100222
MSFT 97)
(XEN) ACPI: HPET 7F67F7A0, 0038 (r1 022210 OEMHPET 20100222
MSFT 97)
(XEN) ACPI: DMAR 7F6880C0, 0090 (r1 AMI OEMDMAR 1
MSFT 97)
(XEN) ACPI: ASPT 7F67FA40, 0034 (r6 022210 PerfTune 20100222
MSFT 97)
(XEN) ACPI: OSFR 7F67FA80, 00B0 (r1 022210 OEMOSFR 20100222
MSFT 97)
(XEN) System RAM: 3880MB (3973552kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:14 APIC version 21
(XEN) Processor #2 7:14 APIC version 21
(XEN) Processor #4 7:14 APIC version 21
(XEN) Processor #6 7:14 APIC version 21
(XEN) IOAPIC[0]: apic_id 7, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3715.495 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) [VT-D]iommu.c:1086: IOMMU: unsupported
(XEN) ---- print_iommu_regs ----
(XEN) drhd->address = fed90000
(XEN) VER = ffffffff
(XEN) CAP = ffffffffffffffff
(XEN) n_fault_reg = 100
(XEN) fault_recording_offset = 3ff0
(XEN) ECAP = ffffffffffffffff
(XEN) GCMD = ffffffff
(XEN) GSTS = ffffffff
(XEN) RTADDR = ffffffffffffffff
(XEN) CCMD = ffffffffffffffff
(XEN) FSTS = ffffffff
(XEN) FECTL = ffffffff
(XEN) FEDATA = ffffffff
(XEN) FEADDR = ffffffff
(XEN) FEUADDR = ffffffff
(XEN) I/O virtualisation disabled
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x25e7000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000160000000->0000000170000000 (935455 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff825e7000
(XEN) Init. ramdisk: ffffffff825e7000->ffffffff8dbd4000
(XEN) Phys-Mach map: ffffffff8dbd4000->ffffffff8e3770f8
(XEN) Start info: ffffffff8e378000->ffffffff8e3784b4
(XEN) Page tables: ffffffff8e379000->ffffffff8e3f0000
(XEN) Boot stack: ffffffff8e3f0000->ffffffff8e3f1000
(XEN) TOTAL: ffffffff80000000->ffffffff8e800000
(XEN) ENTRY ADDRESS: ffffffff81986200
(XEN) Dom0 has maximum 4 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 160kB init memory.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Cui, Dexuan
2010-Mar-31 05:26 UTC
RE: [Xen-devel] VT-d on Asus P7P55D-Evo: IOMMU not supported
I think the BIOS is broken with respect to VT-d. Please try to update to the
latest BIOS.
Thanks,
-- Dexuan
-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Mark Hurenkamp
Sent: 2010年3月31日 4:58
To: xen-devel@lists.xensource.com
Subject: [Xen-devel] VT-d on Asus P7P55D-Evo: IOMMU not supported
Hi,
Having updated my Xen to 4.0-rc9-pre recently, i decided to try
booting without the iommu=0 flag.
The system doesn't crash now (which is an improvement), but gracefully
disables VT-d due to an
unsupported IOMMU.
I've attached the output of xm dmesg, hope it is of use to someone.
Do let me know if there's something more i can do to help in getting
VT-d working on this board.
Regards,
Mark.
__ __ _ _ ___ ___ ___
\ \/ /___ _ __ | || | / _ \ / _ \ _ __ ___ / _ \ _ __ _ __
___
\ // _ \ '_ \ | || |_| | | | | | |__| '__/ __| (_) |__| '_ \|
'__/ _ \
/ \ __/ | | | |__ _| |_| | |_| |__| | | (__ \__, |__| |_) | |
| __/
/_/\_\___|_| |_| |_|(_)___(_)___/ |_| \___| /_/ | .__/|_|
\___|
|_|
(XEN) Xen version 4.0.0-rc9-pre (root@karpeer.net) (gcc version 4.4.1
(Ubuntu 4.4.1-4ubuntu9) ) Mon Mar 29 23:07:18 CEST 2010
(XEN) Latest ChangeSet: Sat Mar 27 16:01:35 2010 +0000
21078:f3db0ae08304
(XEN) Command line:
(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 2 MBR signatures
(XEN) Found 2 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000007f670000 (usable)
(XEN) 000000007f670000 - 000000007f688000 (ACPI data)
(XEN) 000000007f688000 - 000000007f6dc000 (ACPI NVS)
(XEN) 000000007f6dc000 - 000000007f700000 (reserved)
(XEN) 000000007f800000 - 0000000080000000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ffe00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000180000000 (usable)
(XEN) ACPI: RSDP 000FB470, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT 7F670100, 0064 (r1 022210 XSDT2250 20100222
MSFT 97)
(XEN) ACPI: FACP 7F670290, 00F4 (r3 022210 FACP2250 20100222
MSFT 97)
(XEN) ACPI: DSDT 7F6704A0, EF5B (r1 A1290 A1290001 1 INTL
20060113)
(XEN) ACPI: FACS 7F688000, 0040
(XEN) ACPI: APIC 7F670390, 00CC (r1 022210 APIC2250 20100222
MSFT 97)
(XEN) ACPI: MCFG 7F670460, 003C (r1 022210 OEMMCFG 20100222
MSFT 97)
(XEN) ACPI: OEMB 7F688040, 0072 (r1 022210 OEMB2250 20100222
MSFT 97)
(XEN) ACPI: HPET 7F67F7A0, 0038 (r1 022210 OEMHPET 20100222
MSFT 97)
(XEN) ACPI: DMAR 7F6880C0, 0090 (r1 AMI OEMDMAR 1
MSFT 97)
(XEN) ACPI: ASPT 7F67FA40, 0034 (r6 022210 PerfTune 20100222
MSFT 97)
(XEN) ACPI: OSFR 7F67FA80, 00B0 (r1 022210 OEMOSFR 20100222
MSFT 97)
(XEN) System RAM: 3880MB (3973552kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:14 APIC version 21
(XEN) Processor #2 7:14 APIC version 21
(XEN) Processor #4 7:14 APIC version 21
(XEN) Processor #6 7:14 APIC version 21
(XEN) IOAPIC[0]: apic_id 7, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3715.495 MHz processor.
(XEN) Initing memory sharing.
(XEN) VMX: Supported advanced features:
(XEN) - APIC MMIO access virtualisation
(XEN) - APIC TPR shadow
(XEN) - Extended Page Tables (EPT)
(XEN) - Virtual-Processor Identifiers (VPID)
(XEN) - Virtual NMI
(XEN) - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging detected.
(XEN) [VT-D]iommu.c:1086: IOMMU: unsupported
(XEN) ---- print_iommu_regs ----
(XEN) drhd->address = fed90000
(XEN) VER = ffffffff
(XEN) CAP = ffffffffffffffff
(XEN) n_fault_reg = 100
(XEN) fault_recording_offset = 3ff0
(XEN) ECAP = ffffffffffffffff
(XEN) GCMD = ffffffff
(XEN) GSTS = ffffffff
(XEN) RTADDR = ffffffffffffffff
(XEN) CCMD = ffffffffffffffff
(XEN) FSTS = ffffffff
(XEN) FECTL = ffffffff
(XEN) FEDATA = ffffffff
(XEN) FEADDR = ffffffff
(XEN) FEUADDR = ffffffff
(XEN) I/O virtualisation disabled
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) TSC is reliable, synchronization unnecessary
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x25e7000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000160000000->0000000170000000 (935455 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff825e7000
(XEN) Init. ramdisk: ffffffff825e7000->ffffffff8dbd4000
(XEN) Phys-Mach map: ffffffff8dbd4000->ffffffff8e3770f8
(XEN) Start info: ffffffff8e378000->ffffffff8e3784b4
(XEN) Page tables: ffffffff8e379000->ffffffff8e3f0000
(XEN) Boot stack: ffffffff8e3f0000->ffffffff8e3f1000
(XEN) TOTAL: ffffffff80000000->ffffffff8e800000
(XEN) ENTRY ADDRESS: ffffffff81986200
(XEN) Dom0 has maximum 4 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 160kB init memory.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Mark Hurenkamp
2010-Mar-31 20:51 UTC
Re: [Xen-devel] VT-d on Asus P7P55D-Evo: IOMMU not supported
> I think the BIOS is broken with respect to VT-d. Please try to update to > the latest BIOS.Yeah, i figured as much. It''s on the latest Asus Bios though (1307) which was released only a few weeks ago. But since Xen is dumping VT-d related register info, i thought i''d just post them here. Asus doesn''t seem to pay much attention to VT-d issues with their P55 boards, i couldn''t find any indication that they are working on it. I tried to submit a tech support question, but it requires a serial number, which i seem to be unable to locate on the board. Regards, Mark.> Thanks, > -- Dexuan > > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Mark Hurenkamp > Sent: 2010年3月31日 4:58 > To: xen-devel@lists.xensource.com > Subject: [Xen-devel] VT-d on Asus P7P55D-Evo: IOMMU not supported > > Hi, > > Having updated my Xen to 4.0-rc9-pre recently, i decided to try > booting without the iommu=0 flag. > The system doesn''t crash now (which is an improvement), but gracefully > disables VT-d due to an > unsupported IOMMU. > > I''ve attached the output of xm dmesg, hope it is of use to someone. > Do let me know if there''s something more i can do to help in getting > VT-d working on this board. > > Regards, > Mark. > > __ __ _ _ ___ ___ ___ > \ \/ /___ _ __ | || | / _ \ / _ \ _ __ ___ / _ \ _ __ _ __ > ___ > \ // _ \ ''_ \ | || |_| | | | | | |__| ''__/ __| (_) |__| ''_ \| > ''__/ _ \ > / \ __/ | | | |__ _| |_| | |_| |__| | | (__ \__, |__| |_) | | > > | __/ > > /_/\_\___|_| |_| |_|(_)___(_)___/ |_| \___| /_/ | .__/|_| > \___| > > |_| > > (XEN) Xen version 4.0.0-rc9-pre (root@karpeer.net) (gcc version 4.4.1 > (Ubuntu 4.4.1-4ubuntu9) ) Mon Mar 29 23:07:18 CEST 2010 > (XEN) Latest ChangeSet: Sat Mar 27 16:01:35 2010 +0000 > 21078:f3db0ae08304 > (XEN) Command line: > (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 2 MBR signatures > (XEN) Found 2 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009fc00 (usable) > (XEN) 000000000009fc00 - 00000000000a0000 (reserved) > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000007f670000 (usable) > (XEN) 000000007f670000 - 000000007f688000 (ACPI data) > (XEN) 000000007f688000 - 000000007f6dc000 (ACPI NVS) > (XEN) 000000007f6dc000 - 000000007f700000 (reserved) > (XEN) 000000007f800000 - 0000000080000000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000180000000 (usable) > (XEN) ACPI: RSDP 000FB470, 0024 (r2 ACPIAM) > (XEN) ACPI: XSDT 7F670100, 0064 (r1 022210 XSDT2250 20100222 > MSFT 97) > (XEN) ACPI: FACP 7F670290, 00F4 (r3 022210 FACP2250 20100222 > MSFT 97) > (XEN) ACPI: DSDT 7F6704A0, EF5B (r1 A1290 A1290001 1 INTL > 20060113) > (XEN) ACPI: FACS 7F688000, 0040 > (XEN) ACPI: APIC 7F670390, 00CC (r1 022210 APIC2250 20100222 > MSFT 97) > (XEN) ACPI: MCFG 7F670460, 003C (r1 022210 OEMMCFG 20100222 > MSFT 97) > (XEN) ACPI: OEMB 7F688040, 0072 (r1 022210 OEMB2250 20100222 > MSFT 97) > (XEN) ACPI: HPET 7F67F7A0, 0038 (r1 022210 OEMHPET 20100222 > MSFT 97) > (XEN) ACPI: DMAR 7F6880C0, 0090 (r1 AMI OEMDMAR 1 > MSFT 97) > (XEN) ACPI: ASPT 7F67FA40, 0034 (r6 022210 PerfTune 20100222 > MSFT 97) > (XEN) ACPI: OSFR 7F67FA80, 00B0 (r1 022210 OEMOSFR 20100222 > MSFT 97) > (XEN) System RAM: 3880MB (3973552kB) > (XEN) Domain heap initialised > (XEN) Processor #0 7:14 APIC version 21 > (XEN) Processor #2 7:14 APIC version 21 > (XEN) Processor #4 7:14 APIC version 21 > (XEN) Processor #6 7:14 APIC version 21 > (XEN) IOAPIC[0]: apic_id 7, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 3715.495 MHz processor. > (XEN) Initing memory sharing. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging detected. > (XEN) [VT-D]iommu.c:1086: IOMMU: unsupported > (XEN) ---- print_iommu_regs ---- > (XEN) drhd->address = fed90000 > (XEN) VER = ffffffff > (XEN) CAP = ffffffffffffffff > (XEN) n_fault_reg = 100 > (XEN) fault_recording_offset = 3ff0 > (XEN) ECAP = ffffffffffffffff > (XEN) GCMD = ffffffff > (XEN) GSTS = ffffffff > (XEN) RTADDR = ffffffffffffffff > (XEN) CCMD = ffffffffffffffff > (XEN) FSTS = ffffffff > (XEN) FECTL = ffffffff > (XEN) FEDATA = ffffffff > (XEN) FEADDR = ffffffff > (XEN) FEUADDR = ffffffff > (XEN) I/O virtualisation disabled > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) TSC is reliable, synchronization unnecessary > (XEN) Platform timer is 14.318MHz HPET > (XEN) Brought up 4 CPUs > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x25e7000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000160000000->0000000170000000 (935455 pages > to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff825e7000 > (XEN) Init. ramdisk: ffffffff825e7000->ffffffff8dbd4000 > (XEN) Phys-Mach map: ffffffff8dbd4000->ffffffff8e3770f8 > (XEN) Start info: ffffffff8e378000->ffffffff8e3784b4 > (XEN) Page tables: ffffffff8e379000->ffffffff8e3f0000 > (XEN) Boot stack: ffffffff8e3f0000->ffffffff8e3f1000 > (XEN) TOTAL: ffffffff80000000->ffffffff8e800000 > (XEN) ENTRY ADDRESS: ffffffff81986200 > (XEN) Dom0 has maximum 4 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 160kB init memory. > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Mar-31 21:34 UTC
Re: [Xen-devel] VT-d on Asus P7P55D-Evo: IOMMU not supported
On Wed, Mar 31, 2010 at 08:51:01PM +0000, Mark Hurenkamp wrote:> > I think the BIOS is broken with respect to VT-d. Please try to update to > > the latest BIOS. > Yeah, i figured as much. It''s on the latest Asus Bios though (1307) which > was released only a few weeks ago. But since Xen is dumping VT-d related > register info, i thought i''d just post them here. > Asus doesn''t seem to pay much attention to VT-d issues with their P55 > boards, i couldn''t find any indication that they are working on it. > I tried to submit a tech support question, but it requires a serial number, > which i seem to be unable to locate on the board. >Try "dmidecode" in dom0 or on baremetal linux, it might show you the serial.. -- Pasi> Regards, > Mark. > > > Thanks, > > -- Dexuan > > > > -----Original Message----- > > From: xen-devel-bounces@lists.xensource.com > > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Mark Hurenkamp > > Sent: 2010??3??31?? 4:58 > > To: xen-devel@lists.xensource.com > > Subject: [Xen-devel] VT-d on Asus P7P55D-Evo: IOMMU not supported > > > > Hi, > > > > Having updated my Xen to 4.0-rc9-pre recently, i decided to try > > booting without the iommu=0 flag. > > The system doesn''t crash now (which is an improvement), but gracefully > > disables VT-d due to an > > unsupported IOMMU. > > > > I''ve attached the output of xm dmesg, hope it is of use to someone. > > Do let me know if there''s something more i can do to help in getting > > VT-d working on this board. > > > > Regards, > > Mark. > > > > __ __ _ _ ___ ___ ___ > > \ \/ /___ _ __ | || | / _ \ / _ \ _ __ ___ / _ \ _ __ _ __ > > ___ > > \ // _ \ ''_ \ | || |_| | | | | | |__| ''__/ __| (_) |__| ''_ \| > > ''__/ _ \ > > / \ __/ | | | |__ _| |_| | |_| |__| | | (__ \__, |__| |_) | | > > > > | __/ > > > > /_/\_\___|_| |_| |_|(_)___(_)___/ |_| \___| /_/ | .__/|_| > > \___| > > > > |_| > > > > (XEN) Xen version 4.0.0-rc9-pre (root@karpeer.net) (gcc version 4.4.1 > > (Ubuntu 4.4.1-4ubuntu9) ) Mon Mar 29 23:07:18 CEST 2010 > > (XEN) Latest ChangeSet: Sat Mar 27 16:01:35 2010 +0000 > > 21078:f3db0ae08304 > > (XEN) Command line: > > (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 2 MBR signatures > > (XEN) Found 2 EDD information structures > > (XEN) Xen-e820 RAM map: > > (XEN) 0000000000000000 - 000000000009fc00 (usable) > > (XEN) 000000000009fc00 - 00000000000a0000 (reserved) > > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > > (XEN) 0000000000100000 - 000000007f670000 (usable) > > (XEN) 000000007f670000 - 000000007f688000 (ACPI data) > > (XEN) 000000007f688000 - 000000007f6dc000 (ACPI NVS) > > (XEN) 000000007f6dc000 - 000000007f700000 (reserved) > > (XEN) 000000007f800000 - 0000000080000000 (reserved) > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > > (XEN) 0000000100000000 - 0000000180000000 (usable) > > (XEN) ACPI: RSDP 000FB470, 0024 (r2 ACPIAM) > > (XEN) ACPI: XSDT 7F670100, 0064 (r1 022210 XSDT2250 20100222 > > MSFT 97) > > (XEN) ACPI: FACP 7F670290, 00F4 (r3 022210 FACP2250 20100222 > > MSFT 97) > > (XEN) ACPI: DSDT 7F6704A0, EF5B (r1 A1290 A1290001 1 INTL > > 20060113) > > (XEN) ACPI: FACS 7F688000, 0040 > > (XEN) ACPI: APIC 7F670390, 00CC (r1 022210 APIC2250 20100222 > > MSFT 97) > > (XEN) ACPI: MCFG 7F670460, 003C (r1 022210 OEMMCFG 20100222 > > MSFT 97) > > (XEN) ACPI: OEMB 7F688040, 0072 (r1 022210 OEMB2250 20100222 > > MSFT 97) > > (XEN) ACPI: HPET 7F67F7A0, 0038 (r1 022210 OEMHPET 20100222 > > MSFT 97) > > (XEN) ACPI: DMAR 7F6880C0, 0090 (r1 AMI OEMDMAR 1 > > MSFT 97) > > (XEN) ACPI: ASPT 7F67FA40, 0034 (r6 022210 PerfTune 20100222 > > MSFT 97) > > (XEN) ACPI: OSFR 7F67FA80, 00B0 (r1 022210 OEMOSFR 20100222 > > MSFT 97) > > (XEN) System RAM: 3880MB (3973552kB) > > (XEN) Domain heap initialised > > (XEN) Processor #0 7:14 APIC version 21 > > (XEN) Processor #2 7:14 APIC version 21 > > (XEN) Processor #4 7:14 APIC version 21 > > (XEN) Processor #6 7:14 APIC version 21 > > (XEN) IOAPIC[0]: apic_id 7, version 32, address 0xfec00000, GSI 0-23 > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > (XEN) Detected 3715.495 MHz processor. > > (XEN) Initing memory sharing. > > (XEN) VMX: Supported advanced features: > > (XEN) - APIC MMIO access virtualisation > > (XEN) - APIC TPR shadow > > (XEN) - Extended Page Tables (EPT) > > (XEN) - Virtual-Processor Identifiers (VPID) > > (XEN) - Virtual NMI > > (XEN) - MSR direct-access bitmap > > (XEN) HVM: ASIDs enabled. > > (XEN) HVM: VMX enabled > > (XEN) HVM: Hardware Assisted Paging detected. > > (XEN) [VT-D]iommu.c:1086: IOMMU: unsupported > > (XEN) ---- print_iommu_regs ---- > > (XEN) drhd->address = fed90000 > > (XEN) VER = ffffffff > > (XEN) CAP = ffffffffffffffff > > (XEN) n_fault_reg = 100 > > (XEN) fault_recording_offset = 3ff0 > > (XEN) ECAP = ffffffffffffffff > > (XEN) GCMD = ffffffff > > (XEN) GSTS = ffffffff > > (XEN) RTADDR = ffffffffffffffff > > (XEN) CCMD = ffffffffffffffff > > (XEN) FSTS = ffffffff > > (XEN) FECTL = ffffffff > > (XEN) FEDATA = ffffffff > > (XEN) FEADDR = ffffffff > > (XEN) FEUADDR = ffffffff > > (XEN) I/O virtualisation disabled > > (XEN) Total of 4 processors activated. > > (XEN) ENABLING IO-APIC IRQs > > (XEN) -> Using new ACK method > > (XEN) TSC is reliable, synchronization unnecessary > > (XEN) Platform timer is 14.318MHz HPET > > (XEN) Brought up 4 CPUs > > (XEN) *** LOADING DOMAIN 0 *** > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x25e7000 > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Dom0 alloc.: 0000000160000000->0000000170000000 (935455 pages > > to be allocated) > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: ffffffff81000000->ffffffff825e7000 > > (XEN) Init. ramdisk: ffffffff825e7000->ffffffff8dbd4000 > > (XEN) Phys-Mach map: ffffffff8dbd4000->ffffffff8e3770f8 > > (XEN) Start info: ffffffff8e378000->ffffffff8e3784b4 > > (XEN) Page tables: ffffffff8e379000->ffffffff8e3f0000 > > (XEN) Boot stack: ffffffff8e3f0000->ffffffff8e3f1000 > > (XEN) TOTAL: ffffffff80000000->ffffffff8e800000 > > (XEN) ENTRY ADDRESS: ffffffff81986200 > > (XEN) Dom0 has maximum 4 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 160kB init memory. > > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Christian Tramnitz
2010-Mar-31 22:29 UTC
[Xen-devel] Re: VT-d on Asus P7P55D-Evo: IOMMU not supported
31.03.2010 22:51, Mark Hurenkamp wrote:> Asus doesn''t seem to pay much attention to VT-d issues with their P55 > boards, i couldn''t find any indication that they are working on it. > I tried to submit a tech support question, but it requires a serial number, > which i seem to be unable to locate on the board.Even if you find the serial and open the support case there will be no meaningful answer just "Linux is not supported". Been there, done that.... Best regards, Christian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-01 05:50 UTC
Re: [Xen-devel] Re: VT-d on Asus P7P55D-Evo: IOMMU not supported
On Thu, Apr 01, 2010 at 12:29:03AM +0200, Christian Tramnitz wrote:> 31.03.2010 22:51, Mark Hurenkamp wrote: > > Asus doesn''t seem to pay much attention to VT-d issues with their P55 > > boards, i couldn''t find any indication that they are working on it. > > I tried to submit a tech support question, but it requires a serial number, > > which i seem to be unable to locate on the board. > > Even if you find the serial and open the support case there will be no > meaningful answer just "Linux is not supported". Been there, done that.... >Please see here: http://wiki.xensource.com/xenwiki/XenPCIpassthrough Especially this: "Intel developers also want to know about broken IOMMU/VT-d BIOS implementations, see this email: http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00841.html, so let them know all the details about your hardware and software if you have broken BIOS. " -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Apr-09 13:48 UTC
Re: [Xen-devel] Re: VT-d on Asus P7P55D-Evo: IOMMU not supported
On Thu, Apr 01, 2010 at 08:50:24AM +0300, Pasi Kärkkäinen wrote:> On Thu, Apr 01, 2010 at 12:29:03AM +0200, Christian Tramnitz wrote: > > 31.03.2010 22:51, Mark Hurenkamp wrote: > > > Asus doesn''t seem to pay much attention to VT-d issues with their P55 > > > boards, i couldn''t find any indication that they are working on it. > > > I tried to submit a tech support question, but it requires a serial number, > > > which i seem to be unable to locate on the board. > > > > Even if you find the serial and open the support case there will be no > > meaningful answer just "Linux is not supported". Been there, done that.... > > > > Please see here: > http://wiki.xensource.com/xenwiki/XenPCIpassthrough > > Especially this: > "Intel developers also want to know about broken IOMMU/VT-d BIOS implementations, see this email: http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00841.html, so let them know all the details about your hardware and software if you have broken BIOS. "This just got posted on LKML that might shed the light on why certain motherboards have VT-d working i7 but not with i5 CPUs: (https://lists.linux-foundation.org/pipermail/iommu/2010-April/002268.html): " When using iommu_domain_alloc with the Intel iommu, the domain address width is always initialized to 48 bits (agaw 2). This domain->agaw value is then used by pfn_to_dma_pte to (always) build a 4 level page table. However, not all systems support iommu width of 48 or 4 level page tables. In particular, the Core i5-660 and i5-670 support an address width of 36 bits (not 39!), an agaw of only 1, and only 3 level page tables. My patch delays the domain initialization until the first iommu_attach_device, ... _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel