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-users

Re: [Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead

To: "Florian Engelmann (Manntech)" <florian.engelmann@xxxxxxxxxxx>
Subject: Re: [Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead
From: Christian Horn <chorn@xxxxxxxxxxxx>
Date: Tue, 11 Sep 2007 20:12:21 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 11 Sep 2007 11:12:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <NJEJKCJMDNJADDKDHDBPKECOCBAA.florian.engelmann@xxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <NJEJKCJMDNJADDKDHDBPKECOCBAA.florian.engelmann@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Mon, Sep 10, 2007 at 09:49:10AM +0200, Florian Engelmann (Manntech) wrote:
> 
> ping my Server what also failed. An ifconfig gives me an eth0 device with my
> local IP 192.168.1.6 a lo device a peth0 device a vif0.0 device and a xenbr0
> device without any IP. I did not modify the /etc/xen/xend-config.sxp and my
> /etc/network/interfaces looks like this:
> 
> iface eth0 inet static
> iface eth3 inet static
> 
> 
> While eth0 is my default LAN interface and eth3 is my crossover interface to
> the 2nd clusternode. If I change
> 
> (network-script network-bridge)
> to
> (network-script 'network-bridge netdev=eth1')

eth3 is configured with an other ip, and eth1 is the one to be enslaved into
the bridge with the domUs?
Would be an internal-only bridge this way without doing routing.
If this is wanted you should assign an ip to eth1 for debugging, to see if
it can reach the domUs.

Christian

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