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 device not owned by pciback.

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] pci device not owned by pciback.
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Mon, 03 May 2010 08:23:42 -0400
Cc: "Sergio Charpinel Jr." <sergiocharpinel@xxxxxxxxx>
Delivery-date: Mon, 03 May 2010 05:25:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <w2rfca1d54a1005030447ubdb8fcdfp57471d867a7e26dd@xxxxxxxxxxxxxx>
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> <1272393974.3080.37.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <o2nfca1d54a1004280749u46e92074o5ceb2b86dc1801b@xxxxxxxxxxxxxx> <1272476279.3080.46.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1272481985.3080.50.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <o2yfca1d54a1004281514wa895227cg8a4d92d01fa78375@xxxxxxxxxxxxxx> <1272501761.3080.52.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1272551177.3080.66.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <q2yfca1d54a1004290749ha5bd37abt26a3717df33429ef@xxxxxxxxxxxxxx> <1272553796.3080.75.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <w2rfca1d54a1005030447ubdb8fcdfp57471d867a7e26dd@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2010-05-03 at 08:47 -0300, Sergio Charpinel Jr. wrote:
> Ok James,
> 
> I think that you forgot some steps. Do this, renaming your pci device,
> initrd and kernel names:
> 
> # echo "options pciback hide=(41:00.0)" >> /etc/modprobe.conf
> # cd /boot
> # cp initrd-2.6.27.19-5-xen initrd-2.6.27.19-5-xen.save
> # mkinitrd -f --with=pciback --preload=pciback initrd-2.6.27.19-5-xen
> 2.6.27.19-5-xen
> 
> You could also try to specify your SCSI driver name in
> /etc/modules.conf, before making the image.
> 
> Hope this helps.

Sergio,

I appreciate all your help. I was able to get this working this weekend
and was going to update this thread this morning. The steps are very
close to what you have above:

Add the following to /etc/modprobe.conf.local (or modprobe.conf on
non-SLES systems):
options pciback hide=(0000:0e:04.0)(0000:0e:04.1)

Edit /etc/sysconfig/kernel and add 'pciback' to the INITRD_MODULES line.
Rebuild the initrd using `mkinitrd` (just run mkinitrd as root)

#find the device driver that might have the card right now
find /sys/bus/pci/drivers -name 0000:0e:04.0

Based on results of find, add these lines to /etc/init.d/after.boot:
echo -n "0000:0e:04.0"  > "/sys/bus/pci/drivers/mptspi/unbind"  
echo -n "0000:0e:04.1"  > "/sys/bus/pci/drivers/mptspi/unbind"
echo -n "0000:0e:04.0" > /sys/bus/pci/drivers/pciback/new_slot
echo -n "0000:0e:04.0" > /sys/bus/pci/drivers/pciback/bind
echo -n "0000:0e:04.1" > /sys/bus/pci/drivers/pciback/new_slot
echo -n "0000:0e:04.1" > /sys/bus/pci/drivers/pciback/bind

When the system boots up I can now successfully start the virtual
machine and it gets the PCI card. Woohoo!!! 

As a side note, I really don't care much for SLES's after.local. It
doesn't seem to work quite as well as Redhat's rc.local, but thankfully
these commands do work. I'm also not sure what will happen if xendomains
starts my virtual machine, because I don't know if after.local has run
yet. 

Thanks again for all of your help!!!!

James


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

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