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] Yet Another PCI passthrough question

To: James Pifer <jep@xxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Yet Another PCI passthrough question
From: "Beasley, Julien" <Julien.Beasley@xxxxxxx>
Date: Thu, 1 Sep 2011 13:17:39 -0500
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 01 Sep 2011 11:18:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1314886850.542.9.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <1FD06C1B2A7E4842A38834B8AB5B3CFE0326599B91@xxxxxxxxxxxxxxxxxxx> ,<1314823434.9190.3.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1FD06C1B2A7E4842A38834B8AB5B3CFE03265E6363@xxxxxxxxxxxxxxxxxxx> <1314886850.542.9.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxosmBV7BMaUWpHSKu/SKj9P+3jXgAIHxAA
Thread-topic: [Xen-users] Yet Another PCI passthrough question
Thank you very much, James, that worked! I'm going to post exactly what I did 
for future people that encounter the same problem.

// first check that nothing shows in lsmod
# lsmod | grep pciback
# 

// now type modprobe
# modprobe pciback

// now try the lsmod again. Note I had to wait a minute or so.. at first 
nothing was showing up
# lsmod | grep pciback
pciback                50301  0 
xenbus_be               4261  5 pciback,usbbk,netbk,blkbk,blktap

// now do the step James suggested
# echo -n "0000:04:00.0" > "/sys/bus/pci/drivers/pciback/new_slot"

# echo -n "0000:04:00.0" > "/sys/bus/pci/drivers/pciback/bind"

// check that lspci shows pciback in use
# lspci -v
04:00.0 Display controller: ATI Technologies Inc Device 671d
        Subsystem: ATI Technologies Inc Device 1b2a
        Flags: fast devsel, IRQ 24
        Memory at d0000000 (64-bit, prefetchable) [disabled] [size=256M]
        Memory at fe6e0000 (64-bit, non-prefetchable) [disabled] [size=128K]
        I/O ports at e000 [disabled] [size=256]
        Expansion ROM at fe6c0000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 
<?>
        Capabilities: [150] Advanced Error Reporting
        Kernel driver in use: pciback


// so far this works, and I can see the kernel driver in pciback. Good!

// Xen wiki says to check this and not proceed if empty
# xm pci-list-assignable-devices

// that was still empty... but let's keep going anyways


// edit the config to pass the pci device
# vi /etc/xen/vm/windowsvistax64
...
pci= [ '04:00.0' ]


// check that nothing is assigned to the pci list for that VM
# xm pci-list windowsvistax64

// now create the VM
# xm create windowsvistax64

// checkt hat something is assigned to the vm now
xm pci-list windowsvistax64
VSlt VFn domain bus  slot func
0x05 0x0 0x0000 0x04 0x00 0x0


// then I opened the VM graphics console, and it indeed saw my card. Thank you 
James for your help!

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