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-devel] more on current pull

To: "James Harper" <JamesH@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] more on current pull
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 13 Jul 2004 01:17:34 +0100
Cc: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxx>, "ron minnich" <rminnich@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Tue, 13 Jul 2004 01:20:08 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 13 Jul 2004 10:07:16 +1000." <AEC6C66638C05B468B556EA548C1A77D3BDC7B@trantor>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > When you run "xend start", you should see a bridge device being
> > created (xen-br0), and the IP address and routes that previously
> > were set up for eth0 being transferred to xen-br0. Doing the
> > transfer is necessary because of an oddity in the Linux bridge
> > code.
> How can I stop this behaviour? I set up my own bridges in
> /etc/network/interfaces eg:
> And i'd much rather xend not create the bridge for me. Imho, it is not
> xend's place to create the bridge, just to add vif's to bridges, and it
> would muck up firewall rules that rely on interface specifications if on
> boot the interface is eth0 then later on xen-br0.

Yep, if you've got a complicated setup you certainly don't want
xend messing with it.

If you've already got everything setup how you want before xend
starts, then just edit /etc/xen/xend-config.sxp to set:
 (network-script /bin/true)  

Thus, it won't execute /etc/xen/network at all.

You might find some of the stuff in /etc/xen/network useful, in
which case rename it and edit it to suit.

/etc/xen/network is just there to help out the majority of people
who have one physical interface and a single bridge and want
things working straight out of the box.


This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
Xen-devel mailing list