RE: [Xen-users] RE: adding a second NIC

[<joel.coopersmith@xxxxxxxxxxxxx>]

I have restarted the service with no apparent changes, so I took the big
leap and rebooted the Dom0 server.  When it came up I still could not
see the additional bridged eth1.  

[root@testvs ~]# brctl show
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.000000000000       no
xenbr0          8000.feffffffffff       no              peth0
                                                        vif0.0

Here is the contents of my xend-config.sxp file:

[root@testvs ~]# grep -v ^# /etc/xen/xend-config.sxp
(xend-unix-server yes)
(xend-unix-path /var/lib/xend/xend-socket)
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
(network-script network-bridge)
(network-script my-network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 256)
(dom0-cpus 0)
(vncpasswd '') 

Here is my wrapper script:

[root@testvs ~]# cat /etc/xen/my-network-bridge
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$0" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$0" vifnum=1 netdev=eth1 bridge=xenbr1
bridge=xenbr1


Here are what my system thinks it has for network interfaces:

[root@testvs ~]# ifconfig -a |grep Link
eth0      Link encap:Ethernet  HWaddr 00:1B:78:B5:45:4F
          inet6 addr: fe80::21b:78ff:feb5:454f/64 Scope:Link
eth1      Link encap:Ethernet  HWaddr 00:50:BA:7D:6A:28
          inet6 addr: fe80::250:baff:fe7d:6a28/64 Scope:Link
lo        Link encap:Local Loopback
peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
sit0      Link encap:IPv6-in-IPv4
veth1     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
veth2     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
veth3     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
vif0.2    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
vif0.3    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Rainer
Sokoll
Sent: Monday, April 21, 2008 4:15 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] RE: adding a second NIC

On Mon, Apr 21, 2008 at 03:57:39PM -0500, joel.coopersmith@xxxxxxxxxxxxx
wrote:

> Do I need to restart the xend service to make those changes take
affect?

Yes, it is the easiest way.

> How will I see those changes to know they are working?

brctl show

> Then I assume to add them to each guest I modify the 
> /etc/xen/guestname file by replacing the old vif info with the new
device?

With the new bridge, to be correct.

> I see there is
> a MAC address in this same /etc/xen/guestname file that does not seem 
> to correspond to anything in an ifconfig -a.  I am confused as to 
> where this MAC comes from.

The MAC in the guest's config sets the guests's MAC, so you have to run
ifconfig in the corresponding domU.

Rainer

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



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.

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