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] Daily Xen Builds

To: "David F Barrera" <dfbp@xxxxxxxxxx>, "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Daily Xen Builds
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Tue, 16 Aug 2005 12:41:07 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Aug 2005 04:39:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWh4dqNiVUwRDdZRgGy0/fcyGJnAgAOZ6cg
Thread-topic: [Xen-devel] Daily Xen Builds
>> What happens if you do:
>>
>>   ifconfig xen-br0
>>   ifconfig xen-br0 upbl2-1:~ # ifconfig xen-br0
>
>xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>          BROADCAST MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
>bl2-1:~ # ifconfig xen-br0 up
>
>At this point, networking is up. But we knew that--we put that on the
>bug--when we manually bring up xen-br0, networking resumes. I guess the
>question is why xen-br0 is not coming up.
>

I meet this problem both on X86 and X86_64 platform. I also tried
"ifconfig xen-br0 up", but network still couldn't work.

I noticed that after xend start, both eth0 and peth0 have the same IP
address. 
"route" command won't display default gateway. 
"route -n" could see peth0 has the 0.0.0.0 destination. 

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