Re: [Xen-users] Re: Communicating with VM before Network is configured.

["Chris McKeever" <techjedi@xxxxxxxxx>]

On 7/17/06, tbrown@xxxxxxxxxxxxx <tbrown@xxxxxxxxxxxxx> wrote:
>    extra="NBDHOST=65.39.183.43 NBDPORT=8001
>       ip=192.168.2.254:1.1.1.1:192.168.2.86:255.255.255.0"
>
> for an init script it's really simple, as those NBD* parms are already
> loaded into environment variables :) ... but in the more general
> case you would need to parse them out of /proc/cmdline
>
> I don't believe xen has any specific methods for passing config
> parameters to the domU, but I'm no expert.
>
> Oh, and looking back at the subject line... those ip config parameters
> might be of use to you... ip=192...
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?

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