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

Re: [Xen-users] xenbr0 disappeared

To: deshantm@xxxxxxxxx
Subject: Re: [Xen-users] xenbr0 disappeared
From: Asim <linkasim@xxxxxxxxx>
Date: Tue, 1 Jul 2008 21:18:54 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 01 Jul 2008 19:19:27 -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=VusqMdtrBWdmpF6wqdnyl+Lsyg/NNRhJ+9MTsg++qGQ=; b=MZsD5H0DQAq7l9x6FHQhqnnEQRoyXOY37O1gI4hNOWqNjldtOouGTsRY1X3JwRSjxC KgdyTa+DIUlfnMKJ+zBy9uNs6Nc3EF6jXhcPsf/IOxh+5hJD4HekUih7fOj5BXDbSqrZ W2I71YNH1Vw9DkSN2BBoikyOd3HEm0mPkBOkc=
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=uLNuOdlXMDy+RYE6jmzPaJqTnW7VAzXxq2obcgxaJatKHh4piYHRv0yi8lSsRIiCKi Os7pQELRws3OH1JW34quQfeDNyyw+VodMNLwepI+Ai+bjGUVFBHikt2/LZCSqivZ3P5O uSoa8xkGXdKHDctgQ603aRRs0XyTwuoqY30pU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1e16a9ed0807011856n3be7429du36e8e0c212c83339@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> <7ef321c10807011850x200b0934m209bf957fda52333@xxxxxxxxxxxxxx> <1e16a9ed0807011856n3be7429du36e8e0c212c83339@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Todd, I added IPADDR in the ifcfg-eth0 file and it worked. Thanks a lot.

-Asim

On 7/1/08, Todd Deshane <deshantm@xxxxxxxxx> wrote:
>>
>>
>> At domU:
>>
>> eth0      Link encap:Ethernet  HWaddr 00:16:3E:6F:CF:77
>>          inet6 addr: fe80::216:3eff:fe6f:cf77/64 Scope:Link
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          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:127.0.0.1  Mask:255.0.0.0
>>          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)
>>
>>
> eth0 in the domU doesn't have an IP address. It needs one, either static or
> dhcp.
>

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

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