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: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxx>, "ron minnich" <rminnich@xxxxxxxx>
Subject: RE: [Xen-devel] more on current pull
From: "James Harper" <JamesH@xxxxxxxxxxxxxxxx>
Date: Tue, 13 Jul 2004 10:07:16 +1000
Cc: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 13 Jul 2004 01:08:50 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
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
Thread-index: AcRoa5ZGhskyCf7BTWeJTURUfAsMeQAAPCPQ
Thread-topic: [Xen-devel] more on current pull
> 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:

auto br0
iface br0 inet static
  bridge_ports eth0
  up sleep 10 && ifconfig eth0 promisc

(that last line is because of a bug in the tlan network driver re:
promisc mode - I've sent a patch to the lkml but it's so far just been

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.

Other things that might break on changing interfaces midstream are:
static routes

I understand that xend doing this means that it 'just works' for anyone
trying out xen with a reasonably standard config, but it's just a pain
for me.

Any ideas?



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