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


[Xen-users] network-bridge breaks networking when eth0:1 is added

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] network-bridge breaks networking when eth0:1 is added
From: Kai Schaetzl <maillists@xxxxxxxxxxxxx>
Date: Mon, 27 Apr 2009 01:47:07 +0200
Delivery-date: Sun, 26 Apr 2009 16:47:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-users@xxxxxxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I added a virtual interface eth0:1 on one of my machines and suddenly 
networking breaks on startup of the system (eth0 is gone) when xend starts 
and runs the network-bridge script. This is supposed to be fixed according 
to: https://bugzilla.redhat.com/show_bug.cgi

I checked and the network-bridge script contains this fix. It works fine 
on one of my PCs when eth0:1 is added, but not on this one. The one where 
it works runs Xen 3.2.1, the one where it doesn't work runs Xen 3.3.1. 
Both are CentOS 5.3. I compared the scripts and both are absolutely 
identical in this area. I also copied the 3.2.1 script over to the problem 
machine and get the same problem. So, it's probably not Xen version 
Another difference is that the problem machine has also eth1 and eth2 and 
I first assumed the problem might be associated to that. But it happens 
even with eth1 and eth2 disabled.

I can reproduce the problem when I boot with xend disabled. When I then 
start xend I get the error message as described in the bug report and eth0 
is killed. I can then restart the network and all is well. Also, after I 
started xend *once* it seems I can restart it and the problem does *not* 
reappear. It seems to happen only on the first start of xend and not 
thereafter. Which is rather weird, isn't it?

Anyone knows how to fix this or find the cause?


Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com

Xen-users mailing list