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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-users] Follow up: eth0 not getting an inet4 addr using DHCP

from [Digvijoy Chatterjee] [Permanent Link][Original]
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Follow up: eth0 not getting an inet4 addr using DHCP
From: Digvijoy Chatterjee <digvijoy_chatterjee@xxxxxxxxxxx>
Date: Thu, 18 Aug 2005 12:52:04 +0530
Delivery-date: Thu, 18 Aug 2005 07:08:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1124349352.4583.17.camel@xxxxxxxxxxxxxxxxxxxxx>
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>
References: <1124349352.4583.17.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
network restart doesnt help either :

[root@localhost ~]# service network restart
Shutting down interface eth0:  Device eth0 has different MAC address
than expected, ignoring.
[FAILED]
Shutting down loopback interface:  [  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:
Determining IP information for eth0... failed.
[FAILED]



On Thu, 2005-08-18 at 12:45 +0530, Digvijoy Chatterjee wrote:
> I am running two DomUs (FC4) on a Xen0 kernel (2.6.12_1369)
> 
> both of them start up fine ,but VM1 is getting an inet 6 address and i
> am not able to connect to that box remotely..
> .VM2 however has a inet 4 address as you can see below,both use DHCP
> to get an address for eth0
> 
> =\=================================================================
> 
> root@localhost ~]# xm console VM2
> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> 
> Fedora Core release 4 (Stentz)
> Kernel 2.6.11-1.1369_FC4xenU on an i686
> 
> login: root
> Password:
> Last login: Thu Aug 18 12:17:14 on tty1
> [root@localhost ~]# ifconfig
> eth0      Link encap:Ethernet  HWaddr AA:00:00:0E:1A:DF
>           inet addr:172.21.104.228  Bcast:172.21.104.255
> Mask:255.255.255.0
>           inet6 addr: fe80::a800:ff:fe0e:1adf/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:1381 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:124065 (121.1 KiB)  TX bytes:591 (591.0 b)
> 
> 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)
> 
> [root@localhost ~]# --
> ************ REMOTE CONSOLE EXITED *****************
> 
> [root@localhost ~]# xm console VM1
> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> 
> 
> Fedora Core release 4 (Stentz)
> Kernel 2.6.11-1.1369_FC4xenU on an i686
> 
> localhost login: root
> Password:
> Last login: Wed Aug 17 14:21:33 on tty1
> [root@localhost ~]# ifconfig
> eth0      Link encap:Ethernet  HWaddr AA:00:00:23:CE:4C
>           inet6 addr: fe80::a800:ff:fe23:ce4c/64 Scope:Link
> ==================> no inet 4 address for eth0 on VM1
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:326283 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:31463857 (30.0 MiB)  TX bytes:2430 (2.3 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:35 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0[root@localhost ~]# ifconfig
> 
> [root@localhost ~]# ------
> ************ REMOTE CONSOLE EXITED *****************
> 
> This is the Domain-0 ifconfig-->
> 
> eth0      Link encap:Ethernet  HWaddr 00:0B:DB:55:7C:26
>           inet addr:172.21.104.220  Bcast:172.21.104.255
> Mask:255.255.255.0
>           inet6 addr: fe80::20b:dbff:fe55:7c26/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:401275 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7668 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:48502498 (46.2 MiB)  TX bytes:845134 (825.3 KiB)
>           Base address:0xecc0 Memory:ff8e0000-ff900000
> 
> 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:6534 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6534 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1580016 (1.5 MiB)  TX bytes:1580016 (1.5 MiB)
> 
> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:11 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:327633 errors:0 dropped:194 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2430 (2.3 KiB)  TX bytes:31611975 (30.1 MiB)
> 
> vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:16 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2809 errors:0 dropped:144 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1485 (1.4 KiB)  TX bytes:279235 (272.6 KiB)
> 
> xen-br0   Link encap:Ethernet  HWaddr 00:0B:DB:55:7C:26
>           inet addr:172.21.104.220  Bcast:172.21.104.255
> Mask:255.255.255.255
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:240590 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7573 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:25220108 (24.0 MiB)  TX bytes:774018 (755.8 KiB)
> 
>           RX bytes:6149 (6.0 KiB)  TX bytes:6149 (6.0 KiB)
> 
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
> solely for the use of the addressee(s). If you are not the intended
> recipient, please notify the sender by e-mail and delete the original
> message. Further, you are not to copy, disclose, or distribute this e-
> mail or its contents to any other person and any such actions are
> unlawful. This e-mail may contain viruses. Infosys has taken every
> reasonable precaution to minimize this risk, but is not liable for any
> damage you may sustain as a result of any virus in this e-mail. You
> should carry out your own virus checks before opening the e-mail or
> attachment. Infosys reserves the right to monitor and review the
> content of all messages sent to or from this e-mail address. Messages
> sent to or from this e-mail address may be stored on the Infosys e-
> mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-users] eth0 not getting an inet4 addr using DHCP, Digvijoy Chatterjee
Next by Date:  Re: [Xen-users] eth0 not getting an inet4 addr using DHCP, Dirk H. Schulz
Previous by Thread:  [Xen-users] eth0 not getting an inet4 addr using DHCP, Digvijoy Chatterjee
Next by Thread:  Re: [Xen-users] Follow up: eth0 not getting an inet4 addr using DHCP, Derrik Pates
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy