From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Larson Subject: Re: Network still broken, new issue as well , 7468:17a9f111fa93 Date: Tue, 25 Oct 2005 17:28:17 -0500 Message-ID: <435EB181.6000401@us.ibm.com> References: <1129947991.4325.26.camel@pluto.linsolutions.com> <20051025174059.GJ13783@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051025174059.GJ13783@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: Ted Kaczmarek , xen-devel List-Id: xen-devel@lists.xenproject.org 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