Fantu,
Can you try with the attached patch? and pls post the output of “lspci
–v”?
Regards,
Weidong
From:
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Weidong Han
Sent: Friday, January 08, 2010 10:46 AM
To: Pasi Kärkkäinen
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Fantu
Subject: Re: [Xen-devel] Memory mapping for PEG/PCIe Graphics
Passthrough to <any> DomU
Pasi Kärkkäinen wrote:
On Thu, Jan 07, 2010 at 08:14:47AM -0800, Fantu wrote:
i have grub2 also here and i have add dummy=foo before root...
xm dmesg
])
(XEN) [VT-D]dmar.c:548: Host address width 39
(XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbfff000
(XEN) [VT-D]dmar.c:326: endpoint: 0:1b.0
(XEN) [VT-D]dmar.c:557: found ACPI_DMAR_DRHD:
(XEN) [VT-D]dmar.c:374: dmaru->address = fbffe000
(XEN) [VT-D]dmar.c:331: IOAPIC: f0:1f.7
(XEN) [VT-D]dmar.c:331: IOAPIC: 0:13.0
(XEN) [VT-D]dmar.c:386: flags: INCLUDE_ALL
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:446: RMRR region: base_addr ec000 end_address effff
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1d.7
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.0
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.1
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.2
(XEN) [VT-D]dmar.c:326: endpoint: 0:1a.7
(XEN) [VT-D]dmar.c:561: found ACPI_DMAR_RMRR:
(XEN) [VT-D]dmar.c:417: RMRR error: base_addr bf7dc000 end_address bf7dbfff
(XEN) Failed to parse ACPI DMAR. Disabling VT-d.
This looks like you have a buggy BIOS, it doesn't have correct DMAR RMRR table..
When RMRR address range is not in reserved memory (BIOS issue), can use
'iommu_inclusive_mapping=1' to work around it.
So try that options for xen.gz in grub config.
http://wiki.xensource.com/xenwiki/VTdHowTo
yes, obviously the RMRR is setting
incorrectly in BIOS. The base address shouldn't be greater than end address.
"iommu_inclusive_mapping=1" cannot help here. You should report this
issue to the vendor and ask for a correct BIOS.
Regards,
Weidong
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
