WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] how to PCI-passthrough 1 card to a DomU when another @

To: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] how to PCI-passthrough 1 card to a DomU when another @ Dom0 uses the same driver?
From: "dev001" <pgngw+dev001+xen-users@xxxxxx>
Date: Wed, 02 Feb 2011 14:26:19 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 02 Feb 2011 14:27:08 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:from:to:cc:mime-version:content-transfer-encoding:content-type:references:subject:in-reply-to:reply-to:date; s=smtpout; bh=Bmt7G3L6sQSvAdi/Gp1lh725nOc=; b=TSWRdZr1Z+eJzo5LIHVM4KSMIeMVrZ8Top3f4xm/yHcPHIwI4SsBtnYiciS3W3IxLUkdUoBnCZ1WfqTC7x3C+VamRRict22X4f73ocnHAUcKpB2/FxLBcI0FsVps+JiUNDXNRB+jI/Ym54Fm9xdcweClm8/c3BA4jNi7U+WIY9w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1296683031.21707.1418639239@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <1296623011.3053.1418495679@xxxxxxxxxxxxxxxxxxxxxxxxxxx><20110202202705.GD19684@xxxxxxxxxxxx> <1296683031.21707.1418639239@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: pgngw+dev001+xen-users@xxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
hi,

> > Did you follow the rules for doing it detailed in the VT-d howto? Just use 
> > the pciback instead of pci-stub in it.
> i "followed the rules" for method 2 ...

not at all sure why that was NOT working for me, but, the following:

grep pci /boot/grub/menu.lst
        ...
        module /vmlinuz-xen ...
        pci=resource_aligment=0000:05:07.0;0000:02:00.0;0000:03:0.0

rm /etc/modprobe.d/99-local.conf

cat /etc/init.d/boot.local
#! /bin/sh
DEV="0000:02:00.0 \
     0000:03:00.0 \
     0000:05:07.0 \
    "
for BDF in $DEV
do
        [ ! -e /sys/bus/pci/devices/$BDF/driver/unbind ] || \
                echo -n $BDF > /sys/bus/pci/devices/$BDF/driver/unbind
        echo -n $BDF > /sys/bus/pci/drivers/pciback/new_slot
        echo -n $BDF > /sys/bus/pci/drivers/pciback/bind
        echo -n $BDF > /sys/bus/pci/drivers/pciback/permissive
done


now, @ reboot,

dmesg | grep -i seiz
        [   33.277131] pciback 0000:02:00.0: seizing device
        [   33.308782] pciback 0000:03:00.0: seizing device
        [   33.358124] pciback 0000:05:07.0: seizing device

apparently correctly seizes all the devices, as intended. (note the much
later timestamps ...)

and, in my DomU,

lspci
 00:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
 RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
 00:01.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053
 PCI-E Gigabit Ethernet Controller (rev 20)

thanks!

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