On Wed, Feb 24, 2010 at 3:07 PM, Fate <fate@xxxxxxxxxxx> wrote:
> When I run "brctl show", I get this:
>
> bridge name bridge id STP enabled interfaces
> eth0 8000.002219d509ed no vifesty2
> vifwips0
> vifmood0
> vifesty1
> vifesty0
> peth0
>
> If I run "brctl add eth1", it says "device eth1 already exists; can't create
> bridge with the same name". That doesn't seem to make sense, because the
> output above seems to indicate that there is a bridge named eth0 which is
> the name of the device too?
It's part of xen bridge magic. The original device is renamed to
peth0, while a new bridge is created with the name eth0.
> Anyway, can I use any name for the bridge, and
> then do I simply add eth1 to the bridge using brctl addif, and then add the
> new NIC to the domU?
More or less. An example of domU's vif line with two NICs, custom
names, on different bridges look like this
vif = [
'mac=00:16:3E:EC:9F:14, bridge=br102, vifname=dom1-eth0',
'mac=00:16:3E:B5:E7:76, bridge=br68, vifname=dom1-eth1',
]
Also at this point I'd check how Xen behaves after a reboot first.
IIRC, if both eth0 and eth1 is active and has IP address during boot,
the default network script will automatically create bridges for both.
You should make sure this is the case first. If not, see
http://wiki.xensource.com/xenwiki/XenNetworking#head-7b845eda5e0154fecb98165adbd774f6168119d1
on how to have Xen create the bridges.
Personally I don't use Xen's network-bridge script. I comment-it out
from xend-config.sxp, and use OS config files
(/etc/sysconfig/network-scripts/ifcfg* on RHEL) to create the bridges.
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home