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

["Hans Pfeil" <HPfeil@xxxxxxx>]

Jim, thanks for helping me with this.  Anybody and everybody please chime in.  
My last posting was a bit confusing.  I was trying to do it from memory and 
messed it up.  Here is an excerpt from my boot log file.  I totally wiped the 
server and started from scratch.  No wrapper file, no nothing.  Just a clean 
install of SLES10.1 with XEN3.0.  I did setup each NIC with a static IP 
address.  I think the problem is at boot time.  For some reason when I boot to 
XEN, it cannot find these extra nics.   It will see the two embedded Broadcom's 
but not the 8 Intel nics.  The intel nics are:  Intel gigabit VT Quad Port 
Server Adapters, using the Intel 82575 chipset on a Dell 1950 server.  When you 
boot to normal SLES it will see ALL the nics.  Seems to me there is something 
to setup somewhere so XEN can see these cards??


Thanks all,
-Hans


doneSetting up network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8   
done    eth0      device: Broadcom Corporation NetXtreme II BCM5708 Gigabit 
Ethernet (rev 12)
    eth0      configuration: eth-id-00:1e:c9:ad:77:0a
    eth0      IP address: xxx.xxx.xxx.xxx   
done    eth1      device: Broadcom Corporation NetXtreme II BCM5708 Gigabit 
Ethernet (rev 12)
    eth1      configuration: eth-id-00:1e:c9:ad:77:08
    eth1      IP address: xxx.xxx.xxx.xxx   

doneWaiting for mandatory devices:  eth-id-00:1b:21:17:ee:30 
eth-id-00:1b:21:17:ee:31 eth-id-00:1b:21:17:ee:34 eth-id-00:1b:21:17:ee:35 
eth-id-00:1b:21:17:f8:20 eth-id-00:1b:21:17:f8:21 eth-id-00:1b:21:17:f8:24 
eth-id-00:1b:21:17:f8:25 __NSC__
19 18 17 16 15 14 13 12 11 10 8 7 6 5 4 3 2 1 0 
    eth-id-00:1b:21:17:ee:30            No interface found
failed    eth-id-00:1b:21:17:ee:31            No interface found
failed    eth-id-00:1b:21:17:ee:34            No interface found
failed    eth-id-00:1b:21:17:ee:35            No interface found
failed    eth-id-00:1b:21:17:f8:20            No interface found
failed    eth-id-00:1b:21:17:f8:21            No interface found
failed    eth-id-00:1b:21:17:f8:24            No interface found
failed    eth-id-00:1b:21:17:f8:25            No interface found
failedSetting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  
.failed


>>> jim burns <jim_burn@xxxxxxxxxxxxx> 6/19/2008 9:44 PM >>>
On Thursday June 19 2008 03:17:06 pm Hans Pfeil wrote:
> Jim, thanks for your reply.  I have found that XEN is not initializing the
> extra Intel nic's.  I get "failed to initialize".  When I reboot to just
> SLES the nic's are initialized.  Upon rebooting back to XEN "failed to
> initialize in the boot sequence.  I checked the boot log in the
> var/log/boot.msg file and sure enough they "failed to initialize".   Here
> is the ifconfig for both modes.  
>
> 1)  How do you initialize these nic's under XEN mode??

That's puzzling. Once YaST sets up your nics, it should work in either vanilla 
SuSE or xen SuSE. I assume your vanilla & xen kernel versions are exactly the 
same, as is usual for SuSE (and I assume for SLES). Whatever kernel module 
you are using for the Intel nics in vanilla SLES (say e1000?), should show up 
when you do 'modinfo e1000' in xen SLES.

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


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