Re: [Xen-users] pci device not owned by pciback.

To:	James Pifer <jep@xxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-users] pci device not owned by pciback.
From:	"Sergio Charpinel Jr." <sergiocharpinel@xxxxxxxxx>
Date:	Tue, 27 Apr 2010 11:56:48 -0300
Cc:	xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Tue, 27 Apr 2010 07:58:51 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=qZMv+WfCFB9FD7sJxRyTqDZbUvmAs0gZ6rkcJhTfHok=; b=cwys+BHx0NdA9QbDphe6xXiNH5JHEwmsvVTDN1+eJc6O++I4f8O4ZOuMqeT7GIAjLK 0jV2o9DGdJg6Ea5poZ7C5N3pABS+8i/B6bQ4i/rQ1JMEXhcggaZbN9nzeiUQO03RqO0k VO2jNCkWxy63kxKAcLl3DyDBvYiKJCb0y55UY=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ABRyGKZeK+J6qeyLoKJgMdZ2ARYXV9x5Ts69UuM/N/0LUbXVgPDcMzzhkihXCYFMHJ tplZG2amtOredmXDCDW5wxO6u9HQBmg9KbFQJ2m8v4tXqzE7UWEo2mA/RTDOcQUaUzxB 8Ppva84lrgOhZk9w5p/tzOIJHy9Rbl5jiWBdY=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<1272379155.3080.4.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-users-request@lists.xensource.com?subject=help>
List-id:	Xen user discussion <xen-users.lists.xensource.com>
List-post:	<mailto:xen-users@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References:	<1272373556.19411.47.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1272379155.3080.4.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

James,

PV machines do not need VT-d to passthrough.

You need to use pciback.hide in kernel boot line (if pciback is compiled inside the kernel), or make a script to unbind the device. This site explains how.

2010/4/27 James Pifer <jep@xxxxxxxxxxxxxxxx>

On Tue, 2010-04-27 at 09:05 -0400, James Pifer wrote:
> So yesterday I got was able to get a domU successfully using a PCI SCSI
> card. This morning I restarted the host server. When I try to start up
> the same domU I get this error:
>
> Error: pci: improper device assignment specified: pci: 0000:0e:04.0 must
> be co-assigned to the same guest with 0000:0e:04.0, but it is not owned
> by pciback.
>
> How do I make this card owned by pciback on reboot. Do I need to use the
> hide parameter on the kernel line on boot?
>

Looking at this document:
http://wiki.xensource.com/xenwiki/VTdHowTo

It says to add something like this to the module line:
pciback.hide=(01:00.0)(00:02.0)

My kernel version is:
2.6.27.19-5-xen #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/Linux

This page talks about VT and my domU is a PV. Does this same pciback apply?

Thanks,
James

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

--
Sergio Roberto Charpinel Jr.

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

WARNING - OLD ARCHIVES

xen-users

Re: [Xen-users] pci device not owned by pciback.