This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] PCI Passthrough Problems/Questions

To: Nick Couchman <Nick.Couchman@xxxxxxxxx>
Subject: Re: [Xen-devel] PCI Passthrough Problems/Questions
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 25 Oct 2010 14:48:18 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Oct 2010 11:50:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CC5790502000099000BA6DC@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4CC55D5C02000099000BA698@xxxxxxxxxxxxxxxxxxxxx> <20101025174033.GA5766@xxxxxxxxxxxx> <4CC5790502000099000BA6DC@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Mon, Oct 25, 2010 at 12:33:09PM -0600, Nick Couchman wrote:
> On Mon, 2010-10-25 at 13:40 -0400, Konrad Rzeszutek Wilk wrote:
> > 
> > What do you see on your Xen serial output? I presume you cranked up logging:
> > loglevel=all guest_lvl=all iommu=verbose on your Xen command line.
> > 
> > Is there anything that shows up when you get the 'Failed to assign.." ?
> > 
> The only messages I get on the serial console after setting those
> parameters on the xen.gz kernel line in grub (and rebooting, of course)
> are the following:
> (XEN) [VT-D]iommu.c:1496: d0:PCI: unmap bdf = 2:0.0
> (XEN) [VT-D]iommu.c:1364: d1:PCI: map bdf = 2:0.0
> (XEN) domctl.c:848:d0 XEN_DOMCTL_assign_device: assign device (2:0.0)
> failed
> (XEN) event_channel.c:192:d0 EVTCHNOP failure: domain 1, error -22

So, -EINVAL. How comfortable are you sticking a bunch of
dprintk(VTDPREFIX, " in the drivers/passthrough/vtd/iommu.c file? Basically
you need to figure which of the functions that are past line 1364
are being called and return -EINVAL. 

Xen-devel mailing list