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-users

Re: [Xen-users] PCI Passthrough on VTd Enabled Board

To: "Phil Winterfield (winterfi)" <winterfi@xxxxxxxxx>
Subject: Re: [Xen-users] PCI Passthrough on VTd Enabled Board
From: Sadique Puthen <sputhenp@xxxxxxxxxx>
Date: Thu, 14 Aug 2008 13:24:31 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 14 Aug 2008 00:55:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <38AD81989214D54EB5F20C69477AF6C106B83D9C@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <38AD81989214D54EB5F20C69477AF6C106B83D9C@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (X11/20080501)
Phil Winterfield (winterfi) wrote:

I am trying to run a paravirtualized guest OS and use the split driver model on an Intel board with VTd enabled. When I set up the device passthrough as per the xen wiki (http://wiki.xensource.com/xenwiki/VTdHowTo), I find that the device still shows up in dom0 and does not get passed into my guest OS. The xenbus read returns not found for xen-3.0-x86_32p/backend-id.

Can you see anything missing below?

_lspci:_

[root@localhost phil]# lspci

.

.

01:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)

01:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)

02:00.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 09)

_from grub.conf_

title Xen-Fedora Core (2.6.18-xen)

        root (hd0,0)

        kernel /xen.gz com1=115200,8n1 console=com1

module /vmlinuz-2.6.18.8-xen root=LABEL=/ ro xencons=ttyS console=tty0 console=ttyS0, pciback.hide=(01:00.0)(01:00.1)


Most distributions do not compile pciback module statically to the kernel, but as a module. If the pciback support is compiled as a module, adding pciback.hide=(blah)(blah) to kernel is useless. You have to do that in your modprobe.conf and reboot to take that into effect. I do something like the below one in my modprobe.conf.

install bnx2 /sbin/modprobe pciback ; /sbin/modprobe --first-time --ignore-install bnx2
options pciback hide=(0000:09:00.0) verbose_request=1

Obviously make changes wherever required. If pciback is compiled statically to your kernel, your configuration is correct.

--Sadique

        module /initrd-2.6.18-xen.img

_from /etc/xen/pv.conf_

pci = [ '01:00.0', '01:00.1' ]

_from guest OS console_:

************************ NETFRONT for xen-3.0-x86_32p **********

net TX ring size 256

net RX ring size 256

Failed to read xen-3.0-x86_32p/backend-id.

Thread "netfront" exited.

******************* PCIFRONT for device/pci/0 **********

Failed to read device/pci/0/backend-id.

Error ENOENT when reading the backend path device/pci/0/backend

Thread "pcifront" exited.

------------------------------------------------------------------------

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


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

<Prev in Thread] Current Thread [Next in Thread>