[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] using physical NIC

On Fri, 2006-04-07 at 13:23 -0600, Glen Davis wrote:
> I am trying to configure a DOMU (sles10) to use a physical NIC.  This is
> what I have done, and am getting an error.  Am I missing a step?
> Added the pciback.hide to the xen boot.
> title XEN
>     root (hd0,1)
>     kernel /boot/xen.gz 
>     module /boot/vmlinuz-xen root=/dev/sda2 vga=0x314 selinux=0   
> resume=/dev/sda1  splash=silent showopts pciback.hide=(02:06.0)
> (02:06.1)
>     module /boot/initrd-xen
> NEXT ....
> Rebooted to Xen then tried to load a sles10 b9 with the PCI device, and
> I get a pci failed error (see below).
> gdHost-b9:/data1 # xm create -c b9-yast3.conf pci=02:06.0
> Using config file "b9-yast3.conf".
> Copy kernel /boot/vmlinuz-xen from hda2 to
> /var/lib/xen/tmp/vmlinuz.HbFXK3 for booting
> Error: <Fault 2: "pci: failed to locate device and parse it's resources
> - %s[Errno 2] No such file or directory:
> '/sys/bus/pci/devices/0000:02:06.0/driver'">


It appears that your PCI device didn't bind to the pci backend driver
(actually, based on that error message, it appears your device didn't
bind to any driver). If you list the contents of the
'/sys/bus/pci/drivers/pciback' directory, you should see some
(symlink-ed) entries to the devices that the PCI backend "owns". If you
don't see your device (02:06.0) among them, then you'll need to manually
bind it. Try:

echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/bind

and then list the directory's contents. If that fails, check your kernel
logs (dmesg) for any indication of the PCI backend trying to bind to the
device (debug/error lines should start with "pciback").


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.