[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Multiple Bridges Fail to Start


  • To: "Anthony G Angerame" <aga1@xxxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Schober Walter" <Walter.Schober@xxxxxxxxx>
  • Date: Sun, 10 Jun 2007 09:36:21 +0200
  • Delivery-date: Sun, 10 Jun 2007 00:34:06 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Aceq9s8DMLnl1yk1TJGFqbaH6NmtNwAOnqqw
  • Thread-topic: [Xen-users] Multiple Bridges Fail to Start

Hi Tony!

Maybe not a solution to your problem, but it may help you to reach the
target:
I played around with that for days without getting it solved, so I left
that interface thing out of Xen. Means: Configure the Bridges and
Interfaces and all that acc. to your distro, e.g. ifcfg-xenbr0,
ifcfg-xenbr1, ifcfg-eth0, ... on Redhat (I can provide the infos, if you
need them).
Also just replace the network-script with a network-script-dummy, which
simply does nothing.

With that method I managed it to have VLANs on bonding interfaces
bridged into xenbr0 and xenbr1. 
But keep the names xenbr0 and xenbr1 - they are used too often somewhere
;-)

Br
Walter

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Anthony G
Angerame
Sent: Sunday, June 10, 2007 2:32 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Multiple Bridges Fail to Start

Hi,


I am using Xen 3.0.2 on SUSE SLES 10. I have created a 
script in /etc/xen/scripts called "network-mybridges" and 
use two lines to setup xenbr0 and xenbr1. When executed 
manually the script works fine and creates xenbr0 and 
xenbr1. I can then xm create -c <vmname>. with absolutely 
no issues. It just won't work at boot time. It appears 
that the vif-bridge script is shutting down and deleting 
the devices (xenbr) at boot time instead of bringing them 
up. The script is configured into 
/etc/xen/xend-config.sxp.

Here is an excerpt from /var/log/messages:

   2357 May 31 16:57:04 zeus kernel: eth1: no IPv6 routers 
present

2358 May 31 16:57:04 zeus logger: 
/etc/xen/scripts/vif-bridge: online XENBUS_ 
PATH=backend/vif/1/0 2359 May 31 16:57:04 zeus logger: 
/etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/768 
2360 May 31 16:57:04 zeus logger: 
/etc/xen/scripts/vif-bridge: online XENBUS_ 
PATH=backend/vif/1/1 2361 May 31 16:57:04 zeus logger: 
/etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/832


Thanks in advance,


Tony
   2362 May 31 16:57:04 zeus kernel: NET: Registered 
protocol family 17
   2363 May 31 16:57:04 zeus ifup:     vif1.0

2364 May 31 16:57:04 zeus ifup: No configuration found for 
vif1 .0 2365 May 31 16:57:04 zeus ifup: vif1.1 2366 May 31 
16:57:04 zeus ifup: No configuration found for vif1 .1 
2367 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: 
Writing backend/vbd /1/768/node /dev/loop0 to xenstore. 
2368 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: 
Writing backend/vbd /1/768/physical-device 7:0 to 
xenstore. 2369 May 31 16:57:04 zeus logger: 
/etc/xen/scripts/block: Writing backend/vbd 
/1/768/hotplug-status connected to xenstore.

_______________________________________________
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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.