WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Network still broken, new issue as well , 7468:17a9f111f

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Network still broken, new issue as well , 7468:17a9f111fa93
From: Michael Lessard <michael.lessard@xxxxxxxxx>
Date: Tue, 25 Oct 2005 20:10:16 -0400
Cc: Paul Larson <pl@xxxxxxxxxx>, Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 26 Oct 2005 00:07:29 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Hqwrk6UwIo0/3jKJxdlOHmMtG0Sg1K/SHQGgVpi6+Pc1pKDWjIqfSsiPjkfwT77dQvl9HunvbNTo8Ol4MBiVHlEqm8PYJvplGW8BatrW9MlB8c0lq3kIVGUVZ39tV66r3FmrN1eb7oOXDDBqgGTFmR9xZCF3YK01XnCl90SKb9s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051025230136.GB13075@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1129947991.4325.26.camel@xxxxxxxxxxxxxxxxxxxxxx> <20051025174059.GJ13783@xxxxxxxxxxxxxxxxxxxxxx> <435EB181.6000401@xxxxxxxxxx> <20051025230136.GB13075@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On 10/25/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
On Tue, Oct 25, 2005 at 05:28:17PM -0500, Paul Larson wrote:

> Please see bug #363 that's currently biting several of us with systems
> which, for various reasons, use eth1 instead of eth0.  I hope you don't
> mind, I attached logfiles and command output to the bug rather than
> spamming here with it.

I don't mind that at all, no.  In fact, it's much better for me if the logs
are on the bug, and drawing attention to a new bug on the list is good too.

> We have always had to workaround this it seems,
> but were hoping the new script would fix it.  Instead, with the new
> script we just had to find a new workaround.
>
> Basicially, on these systems it assumes eth0 (which we don't use), so we
> never get networking on domU.

I think you want to set, in /etc/xen/xend-config.sxp,

(network-script blade-network)

and then create a file /etc/xen/scripts/blade-network that looks like:

#!/bin/sh

dir=$(dirname "$0")
exec "$dir/network-bridge" "$@" "netdev=eth1"

Don't forget to chmod +x /etc/xen/scripts/blade-network, too.

Hopefully, that will do the trick.  Let me know how you get on.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Bigelow:/etc/xen/scripts# ./blade-network start
/etc/xen/scripts/network-bridge: line 211: /sbin/getcfg: No such file or directory

I use Debian Sid ....



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel