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/
Home Products Support Community News


Re: [Xen-users] xenbr0 disappeared

To: deshantm@xxxxxxxxx
Subject: Re: [Xen-users] xenbr0 disappeared
From: Asim <linkasim@xxxxxxxxx>
Date: Tue, 1 Jul 2008 20:50:39 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 01 Jul 2008 18:51:13 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ADxWScp4+bpYPLIvEqVjcGn2AcBCQK1b0eNUkniP9yw=; b=oqoZe59skYpmd1WXlpwlg+fsVTVJ8j72Lq1vhf4GLFKGP0WKCzVb6jLCC0IWgVByBR TFhQo4hHqSoYJQy72CVnv9l0JlF8QITUj7ytiPaoIjIHtt8GXnOsch3n1oOwBHs1lca4 cNFUqwn3eJ3G+a7cYGY9ALx0rDnMpqhZBYO2Y=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=CGxfKBtmybHQphI5xbZAQBqhiDfPwIsj5OKfK8po/PvlTqazLSQximfRMpAXXfzBjS HlGHa+pZpLqcodhKMY49BT/UVFJ1ubZdVuAt30DLvIUOLJZTAhJ4M4KUCOOqvOmPTNCs 1qrQiOOrzvahf0sBJ/sbv8WjJQ5XNCvCab6aE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1e16a9ed0807011517o30544b70i994be67ff06cfba8@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <7ef321c10806260642o6bbd6a3g5512fe7d71ed41d@xxxxxxxxxxxxxx> <1e16a9ed0806260740qe0e209dv3408fcf69905b561@xxxxxxxxxxxxxx> <7ef321c10806260812m30a8264aj905d76d0e76f142@xxxxxxxxxxxxxx> <1e16a9ed0806260817u6b23bdc9iac8241c5817a13b9@xxxxxxxxxxxxxx> <7ef321c10807010926y5bcc929aoe988ca4514a3747c@xxxxxxxxxxxxxx> <1e16a9ed0807011517o30544b70i994be67ff06cfba8@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thanks a lot Todd for your response.

Yes, I'm using a Xen 3.2. Its a code that I checked out  in May 15 and
built on CentOS 4. The machine(dom0) is connected to internet via
static IP.

eth0 is a bridge. eth1 is an interface that is down currently. I
intend to use eth1 for passthrough I/O but was trying to get bridged
networking working first. I deleted this bridge.

The relevant lines in my sxp are. I'm sorry for the previous
confusion. I corrected it and now sxp looks like:-

(network-script network-bridge netdev=eth0)
(vif-script vif-bridge)

I removed the old bridge. This has made brctl look like:

[root@adsl-02 images]# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00e0815c75c2       no              peth0

At domU:

eth0      Link encap:Ethernet  HWaddr 00:16:3E:6F:CF:77
          inet6 addr: fe80::216:3eff:fe6f:cf77/64 Scope:Link
          RX packets:65 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:47866 (46.7 KiB)  TX bytes:3204 (3.1 KiB)

lo        Link encap:Local Loopback
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  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)

[root@fedora_pristine ~]# ping
connect: Network is unreachable
[root@fedora_pristine ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

The routing table is empty. The ping returns immediately without doing anything.

Am I missing any steps? Shouldnt the domU creation fix the networking.
Do I need to make any changes to sysconfig/network-scripts/* files?


On 7/1/08, Todd Deshane <deshantm@xxxxxxxxx> wrote:
> A few questions/comments..
> Are you using Xen 3.2?
> Why are eth0 and eth1 both bridges?
> in your xend-config.sxp you have two network script lines
> (network-script 'network-bridge netdev=eth0')
> (network-script network-bridge)
> I think that the second overrides the first, you should only use one,
> if you want more bridges you should use a custom script.
> from the guest, do you at least see an eth0 device? what does it
> think it has for routes?
> While the guest is running, do a ping or other network traffic and do
> a trace on the different network cards on dom0 to see if it is being
> picked up.
> What version of xen, how installed, what distro, etc.?
> Cheers,
> Todd

Xen-users mailing list