Re: [Xen-users] Dedicate NIC's to domU's

[jim burns <jim_burn@xxxxxxxxxxxxx>]

On Wednesday June 25 2008 05:20:35 pm Hans Pfeil wrote:
> Thanks so much.  I would have never thought of this.  A coworker suggested
> to INSTALL the drivers in XEN mode.  Didn't think I would have to install
> them twice, once in normal SLES mode and then again in XEN mode.  That did
> the trick.  All is up and running.

Sorry, I never thought that it wasn't a standard SLES kernel module that's 
automatically present. Unlike userland, non-standard kernel modules have to 
be installed for each kernel you have. It was obvious from your hwinfo output 
that the module wasn't being loaded. My next suggestion would have been to do 
a 'modprobe igb' in xen mode. For future debugging methodology reference:

1. boot into xen
2. '/etc/xen/scripts/network-bridge stop'
(The above is done because changes to networking have to be done with xen 
networking down, so that when xen networking restarts, xen picks up the 
changes and creates the proper ethn/pethn pairs.)
3. 'modprobe igb'
4. if 3. errrors, do 'modinfo igb'
5. if 4. also errors, do 'find /lib/modules -name igb.ko' to find out which 
kernels have the igb driver installed. Since in your case, it was installed 
in 2.6.16.54-0.2.5-smp, but wasn't installed in 2.6.16.54-0.2.5-xen, you 
could have taken it from there, and installed it in xen, and rebooted.

3a. if 3. succeeded, you just needed to do '/etc/xen/scripts/network-bridge 
start' to get xen networking back, and find out why the module wasn't loaded 
automatically. 

This all assumes that you are using bridging in your xen network. That can be 
double-checked by looking at /etc/xen/xend-config.sxp: "grep 
network-script /etc/xen/xend-config.sxp|grep -v '#'". For me, I get:

(network-script network-bridge)

If you get network-nat or network-route, you would substitute that above.

Glad you are up.

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