This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Warning wrt starting the xen3.0 network-bridge from init

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Warning wrt starting the xen3.0 network-bridge from init scripts on Gentoo
From: Ernst Bachmann <e.bachmann@xxxxxxxx>
Date: Thu, 3 Nov 2005 00:26:22 +0200
Delivery-date: Wed, 02 Nov 2005 22:23:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <dkbce2$a9b$1@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <dkbce2$a9b$1@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.1
On Wednesday 02 November 2005 22:51, Charles Duffy wrote:
> Gentoo is rather aggressive wrt making sure that dependencies are
> fulfilled.
> This means that running /etc/init.d/net.eth0 restart from an init script
> which declares that it requires a functioning network to work will, if
> no interfaces other than eth0 is configured, cause that init script to
> be told to shut down before the network adapter can be deconfigured!
> So... if you're going to call network-bridge or xend from an init script
> on Gentoo, and that init script declares that it has a dependency on
> having the network up, make sure you have another interface (I use
> dummy0) defined as UP, lest the point in network-bridge where it
> restarts the interface currently being configured result in a very
> confused state.
> (I spent much too much time debugging this issue today).

have a look at /etc/conf.d/rc:

# RC_NET_STRICT_CHECKING allows some flexibility with the 'net' service.
# The following values are allowed:
#  none  - The 'net' service is always considered up.
#  no    - This basically means that at least one net.* service besides net.lo
#          must be up.  This can be used by notebook users that have a wifi 
#          a static nic, and only wants one up at any given time to have the
#          'net' service seen as up.
#  lo    - This is the same as the 'no' option, but net.lo is also counted.
#          This should be useful to people that do not care about any specific
#          interface being up at boot.
#  yes   - For this ALL network interfaces MUST be up for the 'net' service to
#          be considered up.


and, bingo, you can play with your xen bridges without all net-dependend 
services going down...


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>