[Xen-users] [Xen-devel] collecting info on platforms with VT-d BIOS problems

[Pasi Kärkkäinen <pasik@xxxxxx>]

Hello xen-users,

Intel guys are asking for information about systems/motherboards with buggy 
BIOSes 
regarding VT-d (IOMMU) support for PCI passthrough.

If Xen disables VT-d I/O virtualization on your setup because of incorrect 
information 
in BIOS, please post here and/or xen-devel so the Intel guys get to hear about 
it and 
can forward the information to the motherboard/system/BIOS vendor.

Also try updating to the latest BIOS and see if that helps and fixes the 
problem.

Please check "xm dmesg" Xen hypervisor messages for VT-d status on your setup.
You might see errors like:

(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:388: RMRR error: base_addr 0 end_address 0
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.
..
(XEN) I/O virtualisation disabled

Or

(XEN) [VT-D]dmar.c:498: found ACPI_DMAR_RMRR
(XEN) [VT-D]dmar.c:388: RMRR error: base_addr d0000000 end_address cfffffff
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.


Please include the "xm dmesg" log, and also all the information from the mail 
below.
Thanks!

-- Pasi


----- Forwarded message from "Kay, Allen M" <allen.m.kay@xxxxxxxxx> -----

From: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
To: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Cc: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Fri, 22 Jan 2010 16:22:08 -0800
Subject: [Xen-devel] collecting info on platforms with VT-d BIOS problems

We would like to collect information on platforms that have problem with VT-d 
PCI device passthrough using non-IGD PCI devices.  Note that IGD (integrated 
display device) device passthrough code is still being worked on.

If you have encountered  VT-d problems on a particular platform using latest 
xen-unstable, please provide the following information so that we can work with 
OEM's to get their BIOS's fixed:

    (a) Platform details (OEM, Product/Model#,  Other identifying info)
    (b) BIOS version/number
    (c) Version of Xen with which failure is seen (if not the latest 
xen-unstable)
    (d) Specific error/failure details such as serial log

Thanks!

Allen


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

----- End forwarded message -----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users