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

["Dirk H. Schulz" <dirk.schulz@xxxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users