Digvijoy Chatterjee
2005-Aug-18 07:15 UTC
[Xen-users] eth0 not getting an inet4 addr using DHCP
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@lists.xensource.com
http://lists.xensource.com/xen-users
Dirk H. Schulz
2005-Aug-18 07:20 UTC
Re: [Xen-users] eth0 not getting an inet4 addr using DHCP
Digvijoy Chatterjee schrieb:>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 > >Can you post the configs of the vms? Dirk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Digvijoy Chatterjee
2005-Aug-18 07:22 UTC
[Xen-users] Follow up: eth0 not getting an inet4 addr using DHCP
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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Digvijoy Chatterjee
2005-Aug-18 08:16 UTC
Re: [Xen-users] eth0 not getting an inet4 addr using DHCP
configuration for VM1 kernel = "/boot/vmlinuz-2.6.11-1.1369_FC4xenU" ramdisk = "/boot/initrd.img" memory = 256 name = "VM1" nics=1 disk = [ ''phy:hda2,hda2,w'' ] dhcp="dhcp" root = "/dev/hda2 ro" extra = "4 selinux=0" configuration for VM2 kernel = "/boot/vmlinuz-2.6.11-1.1369_FC4xenU" ramdisk = "/boot/initrd.img" memory = 256 name = "VM2" nics=1 disk = [ ''phy:hda1,hda1,w'' ] dhcp="dhcp" root = "/dev/hda1 ro" extra = "3 selinux=0" The Domain-0 FC4 installation has been copied to /dev/hda1 and /dev/hda2 ,its purely an academic setup , all files on /dev/hda1 are same as /dev/hda2 except say /etc/fstab..atleast network scripts r same. Digz On Thu, 2005-08-18 at 09:20 +0200, Dirk H. Schulz wrote:> Digvijoy Chatterjee schrieb: > > >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 > > > > > Can you post the configs of the vms? > > Dirk**************** 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@lists.xensource.com http://lists.xensource.com/xen-users
Derrik Pates
2005-Aug-18 11:07 UTC
Re: [Xen-users] Follow up: eth0 not getting an inet4 addr using DHCP
Digvijoy Chatterjee wrote:> 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]You''ve just pointed out your own problem. Fedora/RH/CentOS network init scripts associate the original MAC address with the network configuration in /etc/sysconfig/network-scripts/ifcfg-eth*, and won''t touch an interface that doesn''t match. Either (a) set a static MAC in your domain configs and fix it in the interface config file, or (b) comment out or remove the line (which starts with ''HWADDR='', I think), and this problem will disappear. -- Derrik Pates demon@devrandom.net _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Unknown
2005-Aug-18 13:00 UTC
Re: [Xen-users] Follow up: eth0 not getting an inet4 addr using DHCP
This is what I did and it works although i don''t understand:
I commented HWADDR in ifcfg-eth0 and restarted the network ,no go ,it
took an inet-6 address and network was unreachable
then i did
root@XenU# ifconfig eth0 down
root@XenU# ifconfig eth0 172.21.104.201 up =====(i chose a purely
random Inet-4 addr in my subnet )
and lo i was connected to the network ,and my broadcast and netmask is
different from Domain-0
i simply dont understand how this is working and i am not too good in
network fundamentals(all services httpd,sshd,etc..are working fine now)
root@XenU# ifconfig
eth0 Link encap:Ethernet HWaddr AA:00:00:46:84:E0
inet addr:172.21.104.201 Bcast:172.21.255.255
Mask:255.255.0.0
inet6 addr: fe80::a800:ff:fe46:84e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2453 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:247257 (241.4 KiB) TX bytes:15740 (15.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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
===============================================================================
[root@localhost Dom-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:20554 errors:0 dropped:0 overruns:0 frame:0
TX packets:1991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2123657 (2.0 MiB) TX bytes:324885 (317.2 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:2500 errors:0 dropped:0 overruns:0 frame:0
TX packets:2500 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:164727 (160.8 KiB) TX bytes:164727 (160.8 KiB)
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:84 errors:0 dropped:0 overruns:0 frame:0
TX packets:1981 errors:0 dropped:151 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13496 (13.1 KiB) TX bytes:189499 (185.0 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:5038 errors:0 dropped:0 overruns:0 frame:0
TX packets:1802 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:379544 (370.6 KiB) TX bytes:288410 (281.6 KiB)
On Thu, 2005-08-18 at 07:07 -0400, Derrik Pates wrote:
> Digvijoy Chatterjee wrote:
> > 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]
>
> You''ve just pointed out your own problem. Fedora/RH/CentOS network
init
> scripts associate the original MAC address with the network
> configuration in /etc/sysconfig/network-scripts/ifcfg-eth*, and
won''t
> touch an interface that doesn''t match. Either (a) set a static MAC
in
> your domain configs and fix it in the interface config file, or (b)
> comment out or remove the line (which starts with
''HWADDR='', I think),
> and this problem will disappear.
>
**************** 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@lists.xensource.com
http://lists.xensource.com/xen-users
Dirk H. Schulz
2005-Aug-19 07:15 UTC
Re: [Xen-users] eth0 not getting an inet4 addr using DHCP
Digvijoy, could you try the following: add a config line for the network interface to the config for each vm which contains a certain mac address and a certain bridge it is put onto. The reason: DHCP has a timeout, and I suspect the timeout for the dhcp call is over before the network is up and the VM on the bridge. If you do not define a mac address, xen has to determine one (and to check if it not already in use) which costs some time. Give it a try. Dirk Digvijoy Chatterjee schrieb:>configuration for VM1 > >kernel = "/boot/vmlinuz-2.6.11-1.1369_FC4xenU" >ramdisk = "/boot/initrd.img" >memory = 256 >name = "VM1" >nics=1 >disk = [ ''phy:hda2,hda2,w'' ] >dhcp="dhcp" >root = "/dev/hda2 ro" >extra = "4 selinux=0" > > >configuration for VM2 > >kernel = "/boot/vmlinuz-2.6.11-1.1369_FC4xenU" >ramdisk = "/boot/initrd.img" >memory = 256 >name = "VM2" >nics=1 >disk = [ ''phy:hda1,hda1,w'' ] >dhcp="dhcp" >root = "/dev/hda1 ro" >extra = "3 selinux=0" > >The Domain-0 FC4 installation has been copied to /dev/hda1 >and /dev/hda2 ,its purely an academic setup , all files on /dev/hda1 are >same as /dev/hda2 except say /etc/fstab..atleast network scripts r same. > >Digz > >On Thu, 2005-08-18 at 09:20 +0200, Dirk H. Schulz wrote: > > >>Digvijoy Chatterjee schrieb: >> >> >> >>>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 >>> >>> >>> >>> >>Can you post the configs of the vms? >> >>Dirk >> >> > > >**************** 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@lists.xensource.com http://lists.xensource.com/xen-users