Xen users - Oct 2006 - e1000: probe of 0000:00:00.0 failed with error -5

I''m having trouble passing 2 ethernet NICs to a DomU.  I''m
referencing:

http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module

The Dom0 kernel seems to be configured correctly.  The pciback module is 
compiled as built-in so I''m passing the pciback.hide on the kernel line
in grub.conf:

module /vmlinuz-2.6.16.28-xen0 root=/dev/md1 pciback.hide=(01:07.0)(01:07.1)

Output of dmesg:

Kernel command line: root=/dev/md1 pciback.hide=(01:07.0)(01:07.1)
...
pciback 0000:01:07.0: seizing device
pciback 0000:01:07.1: seizing device
...

So things seem to be working properly in Dom0.

# lspci
...
01:07.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
Controller (rev 03)
01:07.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
Controller (rev 03)
01:08.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 
5610 (rev 01)
...

Then I''m passing these 2 PCI devices (2 ports on an Intel PRO/1000
PCI-X
dual-port NIC) to the DomU.  The NIC on the motherboard is connected to 
the xenbr0 and we''re passing that address in as well.

vif = [ ''bridge=xenbr0'' ]
pci = [ ''01:07.0'', ''01:07.1'' ]

Here''s output from dmesg in Dom0:

PCI: setting up Xen PCI frontend stub
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
PCI: System does not support PCI
PCI: System does not support PCI
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
pcifront pci-0: Installing PCI frontend
pcifront pci-0: Creating PCI Frontend Bus 0000:00
...
EXT3 FS on sda1, internal journal
Intel(R) PRO/1000 Network Driver - version 6.3.9-k4
Copyright (c) 1999-2005 Intel Corporation.
PCI: Enabling device 0000:00:00.0 (0000 -> 0003)
e1000: probe of 0000:00:00.0 failed with error -5
PCI: Enabling device 0000:00:00.1 (0000 -> 0003)
e1000: probe of 0000:00:00.1 failed with error -5
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda2, internal journal

And output of lspci inside the DomU:

# lspci
00:00.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
Controller (rev 03)
00:00.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
Controller (rev 03)

The e1000 driver is loaded as a module in the DomU kernel (using the 
"e1000" line in modprobe.conf).

==============================
I suspect that the "System does not support PCI" messages might be key
to my problem.  The two PCI devices do seem to be showing up in the DomU 
and it could simply be that I need to add some options to the e1000 line 
in modprobe.conf.  Or maybe I''ve missed a configuration step?

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

Thomas Harold wrote:
> I''m having trouble passing 2 ethernet NICs to a DomU. 
I''m referencing:
> 
>
http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module
> 
> 
> The Dom0 kernel seems to be configured correctly.  The pciback module is 
> compiled as built-in so I''m passing the pciback.hide on the kernel
line
> in grub.conf:
> 
> module /vmlinuz-2.6.16.28-xen0 root=/dev/md1 
> pciback.hide=(01:07.0)(01:07.1)
> 
> Output of dmesg:
> 
> Kernel command line: root=/dev/md1 pciback.hide=(01:07.0)(01:07.1)
> ...
> pciback 0000:01:07.0: seizing device
> pciback 0000:01:07.1: seizing device
> ...
> 
> So things seem to be working properly in Dom0.
> 
> # lspci
> ...
> 01:07.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
> Controller (rev 03)
> 01:07.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
> Controller (rev 03)
> 01:08.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 
> 5610 (rev 01)
> ...
> 
> Then I''m passing these 2 PCI devices (2 ports on an Intel PRO/1000
PCI-X
> dual-port NIC) to the DomU.  The NIC on the motherboard is connected to 
> the xenbr0 and we''re passing that address in as well.
> 
> vif = [ ''bridge=xenbr0'' ]
> pci = [ ''01:07.0'', ''01:07.1'' ]
> 
> Here''s output from dmesg in Dom0:
> 
> PCI: setting up Xen PCI frontend stub
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
> pcifront pci-0: Installing PCI frontend
> pcifront pci-0: Creating PCI Frontend Bus 0000:00
> ...
> EXT3 FS on sda1, internal journal
> Intel(R) PRO/1000 Network Driver - version 6.3.9-k4
> Copyright (c) 1999-2005 Intel Corporation.
> PCI: Enabling device 0000:00:00.0 (0000 -> 0003)
> e1000: probe of 0000:00:00.0 failed with error -5
> PCI: Enabling device 0000:00:00.1 (0000 -> 0003)
> e1000: probe of 0000:00:00.1 failed with error -5
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS on sda2, internal journal
> 
> And output of lspci inside the DomU:
> 
> # lspci
> 00:00.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
> Controller (rev 03)
> 00:00.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet 
> Controller (rev 03)
> 
> The e1000 driver is loaded as a module in the DomU kernel (using the 
> "e1000" line in modprobe.conf).
Have you tried adding this line do a domU''s modprobe.conf?

   "alias eth0 xennet"

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

Mike Wright wrote:
> Have you tried adding this line do a domU''s modprobe.conf?
> 
>   "alias eth0 xennet"
Tried that now, doesn''t seem to have any effect.  Whenever the
"e1000"
module loads (either automatically when the DomU starts or when I 
rmmod/modprobe it after changing the alias line) I''m still seeing the 
probe-failed message.

I''ve even added in (2) 56k modems, passed in via pciback/pcifront and 
they''re showing up fine in the lspci output.  Which I think is more 
evidence that pciback is working properly.

At this point, I''m considering configuring the Dom0 to grab the Intel 
NICs, bond them, and put them on a 2nd bridge (xenbr1) before passing 
them as a vif to the DomU.  The performance hit shouldn''t be too bad 
since it''s only a T1 line on the external side of the Intel NICs and 
this is a dual-core AM2 CPU.

The open question for that solution is whether it''s better to bond NICs
in Dom0 or pass them in via pciback/pcifront and let the DomU do the 
bonding.  If I need to bond in DomU, then I have to get the e1000 driver 
working with pciback/pcifront.

(There was a really old thread where someone ran into this issue, but 
the mailing list archives don''t give enough information to solve the 
issue.  Nor do the follow-up posts give enough of a pointer as to where 
to find the solution information.)

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