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] Networking problems with debian packages

To: Christian Wicke <xen.christian@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Networking problems with debian packages
From: Gerd Knorr <kraxel@xxxxxxxxxxx>
Date: 03 Mar 2005 15:45:11 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Mar 2005 15:59:41 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <200503031213.27518.xen.christian@xxxxxxxxxxxxxxx>
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>
Organization: SUSE Labs, Berlin
References: <200503031213.27518.xen.christian@xxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
Christian Wicke <xen.christian@xxxxxxxxxxxxxxx> writes:

> Does anyone know what is the correct way to make this work?

The xen start script network setup doesn't work very good for me as
well.  Sometimes it works, sometimes it doesn't, havn't figured yet

I simply make eth0 a bridge early in the boot process, before the
network setup.  Hooking into /etc/init.d/boot.local works for me, see
below for the few script lines.  Then let the distribution start
scripts configure the eth0 device as usual.  Disable
/etc/xen/scripts/network (by inserting "exit" at line #2 for example),
so xend will not try to do the bridge setup again.  Configure your xen
domains to use eth0, i.e. "vif = [ 'bridge=eth0' ]".  Works fine for



# make eth0 a bridge
ip link set name hw-eth0 dev eth0
brctl addbr eth0
brctl addif eth0 hw-eth0
ip link set up hw-eth0

#define printk(args...) fprintf(stderr, ## args)

SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list