[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Re: Communicating with VM before Network is configured.
From: Chris McKeever <cgmckeever@xxxxxxxxxxx> Date: Jul 18, 2006 11:21 AM Subject: Re: [Xen-users] Re: Communicating with VM before Network is configured. To: cgmckeever@xxxxxxxxxxx On 7/18/06, Chris McKeever <techjedi@xxxxxxxxx> wrote: > > > > I have been playing with this myself - and I can't seem to get the > > kernel autoconfig working (FC5) - > > My xen kernel has been compiled with the CONFIG_IP_PNP > > option set, and then reboot > > > > I 'try' to pass the kernel the following parameters at boot, but they > > just dont seem to take: > > > > vif = [ 'ip=192.168.1.61' ] > > netmask = "255.255.255.0" > > gateway = "192.168.1.1" > > hostname = "ds-1" > > > > > > any suggestions as to what I may be missing? > If you check this link: http://lists.xensource.com/archives/html/xen-devel/2006-02/msg00147.html you can see that the method you are using, actually (in terms of the referenced doc) is supposed to be available for config parameters: ip="blah" netmask="blah" gateway="blah" the config parameters are also documented in, http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION03210000000000000000 and ip address is stated to be part of vif (of course I may be misinterpretting the use of the ip address in that context) I'll give the extras a try - seems like it should work via the documented way - but it probably does, I am just missing something. > AFAIK, your vif line doesn't need an IP address, as the default scripts > are in bridging mode, and you don't need to tell xen what IP address to > route in bridged mode. The netmask and gateway parameters I've never seen > before. > > If you want/need the kernel to autoconfigure so it can do a network based > boot, then you to copy the parameter format I was using. > > The full kernel command line syntax is > ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> > using the 'extra' parameter seems to have passed all the appropriate network config options based on Tom's suggestion - Any ideas why the network config options don't work as described? http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html#SECTION03210000000000000000 netmask Manually configured IP netmask. gateway Manually configured IP gateway. hostname Set the hostname for the virtual machine > which would be > ip=192.168.1.61:1.1.1.1:192.168.1.1:255.255.255.0 > > for the parameters you have shown above, and that would go into the > "extras" variable... > > > > > Thanks > > Chris > > > > > > > > > You'll need a kernel with autoconfig enabled. > > > > > > -Tom > > > > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@xxxxxxxxxxxxxxxxxxx > > > http://lists.xensource.com/xen-users > > > > > > > > > -- > > ---------------------------------- > > please respond to the list .. if you need to contact me direct > > cgmckeever is the account > > prupref.com is the domain > > > > <A href="http://www.prupref.com">Simply Chicago Real Estate</A> > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@xxxxxxxxxxxxxxxxxxx > > http://lists.xensource.com/xen-users > > > > ---------------------------------------------------------------------- > tbrown@xxxxxxxxxxxxx | Courage is doing what you're afraid to do. > http://BareMetal.com/ | There can be no courage unless you're scared. > | - Eddie Rickenbacker > > _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |