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-bridge defunct

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] network-bridge defunct
From: Michael Lessard <michael.lessard@xxxxxxxxx>
Date: Tue, 25 Oct 2005 15:49:09 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 25 Oct 2005 19:46:21 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=NmwrjmnW9qZMNhWS6/MD3l/FAR4GwjZVL0q4Knn5DHxAmpl7k2psPGlEyd999UfvketGpFBf/rosPi4ghbsK630y3GFpxQOUolxfol2NO3ahozKXI6VQZl+O8tdDlF9fJ7NLWYomdBrnX96AyEo5TNPGMJZAzdo1J+t479VYLNs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <c5530b840510180717w369ba65fh4827aff4d853dd07@xxxxxxxxxxxxxx>
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: <c5530b840510180648m4f89939ewbcdf63b53fa81b30@xxxxxxxxxxxxxx> <20051018140539.GE12489@xxxxxxxxxxxxxxxxxxxxxx> <c5530b840510180717w369ba65fh4827aff4d853dd07@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On 10/18/05, Michael Lessard <michael.lessard@xxxxxxxxx> wrote:


On 10/18/05, Ewan Mellor < ewan@xxxxxxxxxxxxx> wrote:
On Tue, Oct 18, 2005 at 09:48:07AM -0400, Michael Lessard wrote:

> Hi everybody !
>
>  I haved use Xen 2.06 with my two Domains from some months and all working
> pretty good !  Now i have remove Xen 2.06 and put Xen 3 (unstable.hg) , i
> haved build this morning with make world and make install.  My Dom0 and
> DomU starts successfuly, but on my  Dom0  i haved network-bridge defunct
> when i type ps -aux, so you imagne that in DomU netwrok wan't work :(

The defunct network-bridge is not a problem.  There are other problems with
networking, and I'll let other people answer, because I don't have a handle on
them at the moment, but the defunct network-bridge process isn't a problem in
and of itself.

Ewan.

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

If i use brctl to create bridge like in the script,
# brctl addif xen-testbridge eth0  
error on eth0

but if i use :
# brctl addbr xen-testbridge 
# brctl addif xen-testbridge eth0  
no error reported ...

But i thinkg to make it work with Xen, i need other things...




With latest mercurial source, network-bridge defunct is now ok ;) 

But i still could not ping my Dom0 for DomU ...

My setup :
2 Network Carfs on Debian Sid for both of my domains (Dom0 and DomU)
1 network cards (eth0) for my DomU, the config for network cards on Dom0 is :
      iface eth0 inet manual
            up /sbin/ifconfig eth0 up

When i start DomU, i see appear vif1.0 , when i ping Dom0 from Dom0 i see only RX bytes growth

On Dom0 , i have do echo "1" > /proc/sys/net/ipv4/ip_forward  and iptables -P FORWARD ACCEPT

My xen config for DomU :
kernel = "/boot/vmlinuz-2.6.12-xenU"
memory = 200
name = "Albert"
nics=1
vif = [ 'mac=aa:00:00:00:00:11, bridge=xenbr0' ]
disk = [ 'phy:/dev/hdc3,hdc3,w', 'phy:/dev/hdc5,hdc5,w', 'phy:/dev/hdc1,hdc1,w' ]
root = "/dev/hdc3 ro"

I have try with and without mac address specified ...
What's wrong with my setup ? 

thanks

Michael






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>