From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bauer Subject: Re: iommu: mapping reserved region failed - Q35 -VT-DIssue Date: Fri, 31 Oct 2008 17:20:29 +0100 Message-ID: <490B304D.7060000@cubewerk.de> References: <49089D18.4030405@cubewerk.de><4908B669.7080108@cubewerk.de><409D32C55C48D34DB5E31C8AB29EB15B071C6E74@FTLPEXCH05.citrite.net> <4908BC3C.3070307@cubewerk.de> <409D32C55C48D34DB5E31C8AB29EB15B071C6EA7@FTLPEXCH05.citrite.net> <4908C6FC.9030307@cubewerk.de> <715D42877B251141A38726ABF5CABF2C018686CF47@pdsmsx503.ccr.corp.intel.com> <49096151.8090500@cubewerk.de> <715D42877B251141A38726ABF5CABF2C018686D126@pdsmsx503.ccr.corp.intel.com> <49098860.9050309@cubewerk.de> <715D42877B251141A38726ABF5CABF2C018686D17B@pdsmsx503.ccr.corp.intel.com> <4909C811.9070105@cubewerk.de> <715D42877B251141A38726ABF5CABF2C018686D23C@pdsmsx503.ccr.corp.intel.com><490AB8FC.1020807@cubewerk.de><715D42877B251141A38726ABF5CABF2C018686D43D@pdsmsx503.ccr.corp.intel.com><490B16E4.2060604@cubewerk.de><409D32C55C48 D34DB5E31C8AB29EB15B071C7730@FTLPEXCH05.citrite.net> <490B23AC.8020700@cubewerk.de> <409D32C55C48D34DB5E31C8AB29EB15B071C777F@FTLPEXCH05.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <409D32C55C48D34DB5E31C8AB29EB15B071C777F@FTLPEXCH05.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ross Philipson schrieb: > Attached is a printout of your DMAR tables. Focusing on the following failures that occurred later in the boot process: > > (XEN) domain_context_mapping: can't find drhd for device (bus=0 dev=1f func=2) > (XEN) [VT-D]iommu.c:1545:d0 intel_iommu_add_device: context mapping failed > (XEN) domain_context_mapping: can't find drhd for device (bus=0 dev=1f func=5) > (XEN) [VT-D]iommu.c:1545:d0 intel_iommu_add_device: context mapping failed > > The DMAR only has two DRHD with 1 and 3 scope entries respectively for device endpoints (covering devices 00:1b.0, 00:03.0, 00:03.2, 00:03.3). There are no scope entries for entire bridges and there is not an INCLUDE_ALL DRHD. This is what is causing the failure - no match. It seems odd to me that there are so few entries. Is there anything i can do to work on that problem further? Regards -- Stefan