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

[Xen-users] network bridge empty

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] network bridge empty
From: Hans de Bruin <bruinjm@xxxxxxxxx>
Date: Sun, 05 Mar 2006 16:46:12 +0100
Delivery-date: Sun, 05 Mar 2006 15:46:53 +0000
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/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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
My very first xen DomU can not ping anything on my network. Well that is
not entirely true, it can ping itself. I did not touch any of the
scripts in /etc/xen so xen should be using bridging. My pc is running
xen-unstable and uses a 3Com PCI 3c905B

 Just after the 'xen start' on Dom0 brctl shows:

  bash-3.00# brctl show xenbr0
  bridge name     bridge id               STP enabled     interfaces
  xenbr0          8000.000000000000       no

and after DomU is started:

  bash-3.00# brctl show xenbr0
  bridge name     bridge id               STP enabled     interfaces
  xenbr0          8000.feffffffffff       no              vif1.0

Am I missing interfaces on the bride, like vif0.0 for example?

-- 
Hans


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

<Prev in Thread] Current Thread [Next in Thread>