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

xen-users

[Top] [All Lists]

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

To: Christian Horn <chorn@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead
From: Florian Engelmann <mailinglist@xxxxxxxx>
Date: 2007年9月12日 13:22:43 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: 2007年9月12日 04:23:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070911181221.GA25320@xxxxxxxxxxxx>
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> <20070911181221.GA25320@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
Christian Horn schrieb:
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
After some tests it looks like bridgeing with the dell powerdege 2900 onboard broadcom nic does not work. I changed to eth2 (intel pro 1000) and everything works fine. kernel bug?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-users] specs for multiuse xen boks + drbd for redundancy , Ingard Mevåg
Next by Date: Re: [Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead , Christian Horn
Previous by Thread: Re: [Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead , Christian Horn
Next by Thread: Re: [Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead , Christian Horn
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /