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

["Chris McKeever" <techjedi@xxxxxxxxx>]

On 7/19/06, Chris McKeever <techjedi@xxxxxxxxx> wrote:
> On 7/18/06, tbrown@xxxxxxxxxxxxx <tbrown@xxxxxxxxxxxxx> wrote:
> > On Tue, 18 Jul 2006, Chris McKeever wrote:
> >
> > > > Then again, I don't know why the xen code couldn't convert network
> > > > configuration parameters into the kernel auto-config format. I don't know
> > > > if it is a good idea, but it seems possible.
> > >
> > > >From what I have seem - it is supposed to:
> > >
> > > http://www.nabble.com/IP-configuration-for-domU-ignored-t1779301.html
> > >
well - to put this to wraps (at least for my issue) -
I have gotten xen to build the kernel command line network string:

config:

vif = ['']
ip="192.168.1.61"
netmask="255.255.255.0"
gateway="192.168.1.1"
hostname="ds-1"

Result:
Kernel command line:
ip=192.168.1.61:1.2.3.4:192.168.1.1:255.255.255.0:ds-1:eth0:off
root=/dev/sda1 ro

just a side note - the kernel needs to be built with IP autoconfig -
note that the server IP is defaulted when not supplied (as suggessted
by Tom in an earlier post)

> >
> > OK. I've just done some testing. as far as I can see, xen-3.0.2-2
> > does fill in a nfs_server entry of 1.2.3.4 and should avoid the
> > problem I'm describing and that Pablo talks of at the top of that page.
> > But at the bottom he says his problem went away with a recompiled kernel.
> >
> >
> > Anyhow, if you are getting an ip=... kernel parameter with a blank
> > nfs-server entry, you can try adding this to your config file:
> >
> >    nfs_server="4.3.2.1"
> >
>
> are you saying that you are not using the 'extra' variable here - and
> are in fact getting xen to build the command line string for network
> config of the guest via the config (gateway,netmask, etc) parameters?
> If so, that is all I have been on a quest for this whole time.
>
> > When you boot, there should be some "clues"...
> >
> > e.g.
> >
> >    Using config file "test.ip".
> >    Started domain test
> >    Linux version 2.6.16-xenU (root@xxxxxxxxxxxxxxxxxx) (gcc version
> >    3.4.5 20051201 (Red Hat 3.4.5-2)) #3 SMP Tue Jul 18 11:39:43 PDT
> >    <snip>
> > Kernel command line:
> > ip=192.168.2.254:5.4.3.2:192.168.2.86:255.255.255.0::eth0:off
> > root=/dev/nbd0 ro NBDHOST=65.39.183.43 NBDPORT=8000 single
> >    <snip>
> >    Using IPI No-Shortcut mode
> > IP-Config: Complete:
> >       device=eth0, addr=192.168.2.254, mask=255.255.255.0, gw=192.168.2.86,
> >      host=192.168.2.254, domain=, nis-domain=(none),
> >      bootserver=4.3.2.1, rootserver=4.3.2.1, rootpath=
> >    Freeing unused kernel memory: 132k freed
> >    Red Hat nash version 4.2.1.6 starting
> >
> > I've left shifted the clues... e.g. the kernel command line and
> > the IP-Config: settings. If you're not getting an IP-Config
> > setting, then the either your kernel isn't compiled right, or
> > your ip= kernel parameters are not recognized as legit.
> >
>
> your config file here would help - as I no longer know if we are even
> talking the same issue - if all this is still on the 'extra' variable
> - we arent
>
> To asnwer your inquiry - I do get the kernel command line and
> IP-Config settings ONLY when I use the extra variable.  When I rely on
> the individual config parameters - I get nothing in the kernel command
> line except the root definition
>
>
> Thanks
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users