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: Paul Larson <pl@xxxxxxxxxx>
Date: Tue, 25 Oct 2005 17:28:17 -0500
Cc: Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 25 Oct 2005 22:23:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051025174059.GJ13783@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.4.1 (Windows/20051006)
Ewan Mellor wrote:
Regarding your other network problems, if you are still suffering once you've
changed your configuration, then please submit a full set of logs.  The
scripts involved have changed recently, as you know, but they are very
difficult to test, because we don't have a great variation of network
topologies available.  I'd be looking for

ifconfig
brctl show
cat /var/log/syslog
cat /var/log/debug
cat /var/log/xend.log
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. 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.

Thanks,
Paul Larson


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