RE: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue

["Ross Philipson" <Ross.Philipson@xxxxxxxxxx>]

Stefan,

Most of the paths through the function domain_context_mapping() (in
xen/drivers/passthrough/vtd/iommu.c) also trace extra information but I
don't see those traces so it is reasonable to assume that the function
is returning an error when the call to acpi_find_matched_drhd_unit()
fails to find a DRHD for the particular device. I would start by putting
a trace there in the failure case and trace out the bus/dev info
(presumably it is device 00:03.2). If this is the case then we can look
at your DMAR ACPI table - maybe this is a faulty BIOS issue (e.g. there
is no DRHD reporting INCLUDE_ALL devices).

Or I may be wrong and the logging level is just not set for those
gdprintk() calls in trace in the switch statement (though I don't think
this is the case). If it is the case put code after the various calls in
the switch statement to test the "ret" value and trace an error if it
fails.

Thanks
Ross


-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Stefan Bauer
Sent: Friday, October 31, 2008 3:51 AM
Cc: 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35
-VT-DIssue

Han, Weidong schrieb:
> Yes, this output is complete and helpful. I found the problem exists
in domain_context_mapping(), which never succeeds. Thus result in other
problems. Can you add some printk to locate where it fails?

I will if you advice me how to do where exactly.

> In addition, I suggest you don't add extra graphic card into your
machine, as I know it may introduce issues on Q35.  

Problem is that i want to use the pci-e card for my hvm guest and the
onboard one for dom0. it seems that both the onboard and pci-e one
cant work alongside, so iam forced to add another one.

Regards


-- 
Stefan

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

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