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

[James Pifer <jep@xxxxxxxxxxxxxxxx>]

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