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

["Hans Pfeil" <HPfeil@xxxxxxx>]

Well all, I'm making some headway and received a little joy but still have some 
issues.  Here are my stats:

Xen = Xen 3.0
OS = Sles 10.1
NICs = 2, Broadcom's embedded and 2-quad port Intel nics, total of 10 on the 
machine.  In YAST I selected NONE for each of the Intel NIC's.  This was so 
domO would not see it.  Was this correct?

1)  I would like to use the Intel nics for my domU's.

2)  below is a copy of my wrapper file:

# cat /etc/xen/scripts/multi-network-bridge
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" start vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" start vifnum=1 netdev=eth1 bridge=xenbr1
"$dir/network-bridge" start vifnum=2 netdev=eth2 bridge=xenbr2
"$dir/network-bridge" start vifnum=3 netdev=eth3 bridge=xenbr3
"$dir/network-bridge" start vifnum=4 netdev=eth4 bridge=xenbr4
"$dir/network-bridge" start vifnum=5 netdev=eth5 bridge=xenbr5
"$dir/network-bridge" start vifnum=6 netdev=eth6 bridge=xenbr6
"$dir/network-bridge" start vifnum=7 netdev=eth7 bridge=xenbr7
"$dir/network-bridge" start vifnum=8 netdev=eth8 bridge=xenbr8

3)  below is what I get when I type brctl show

# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000000000000       no
xenbr1          8000.feffffffffff       no              vif0.1
                                                        peth1
xenbr2          8000.000000000000       no
xenbr3          8000.000000000000       no

4)  below is the notification I'm receiving:  notice after xenbr3 the errors 
regarding line 225 and the missing veth's.  Not sure where to go from here.  Is 
my wrapper file correct? 




eth1      Link encap:Ethernet  HWaddr 00:1E:C9:AD:77:08
          inet addr:xxxxxxx  Bcast:xxxxxxxxxx  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1063 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:124554 (121.6 Kb)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:428 errors:0 dropped:0 overruns:0 frame:0
          TX packets:428 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:27293 (26.6 Kb)  TX bytes:27293 (26.6 Kb)

peth1     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1063 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:128806 (125.7 Kb)  TX bytes:0 (0.0 b)
          Interrupt:16 Memory:da000000-da012100

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1063 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:124554 (121.6 Kb)

xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1063 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:109672 (107.1 Kb)  TX bytes:0 (0.0 b)

xenbr2    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

xenbr3    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

~ # sh /etc/xen/scripts/multi-network-bridge start
/etc/xen/scripts/network-bridge: line 226: /etc/sysconfig/network/ifcfg-: No 
such file or directory
/etc/xen/scripts/network-bridge: line 226: /etc/sysconfig/network/ifcfg-: No 
such file or directory
/etc/xen/scripts/network-bridge: line 226: /etc/sysconfig/network/ifcfg-: No 
such file or directory

Link veth4 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.

Link veth5 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.

Link veth6 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.

Link veth7 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.

Link veth8 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports.  If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.






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