Forwarding to devel list. (changed the wordings bit) The xmexample1 seems to contain hostname= "vm%d" % vmid Does this work with HVM ? I tried setting hostname=foo for my HVM based FC5 Linux domU. It does not seem to work. Also, is there a way to set IP address for a Linux HVM DomU ? I have seen somewhere (not in xen example) vif = [ ''ip=192.168.1.12'' ] How do both these work ? (if they are supposed to work ) Are some scripts run after DomU is instantiated ? OR are passed as kernel params ? Thanks /Jd ps. anyone using these params, can u please send me output of cat /proc/cmdline from DomU --------------------------------- Cheap Talk? Check out Yahoo! Messenger''s low PC-to-Phone call rates. --------------------------------- Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I strongly dislike the {ip, dhcp, root*} options. They map to Linux
kernel options. If someone wants to do that in the configuration
instead of a bootloader configuration, I think the should use the
ill-named ''extra'' option, which is appended to the kernel
command line.
This is for paravirtualized linux domU''s.
Would be best if ip configuration is done in userspace of the guest
unless someone would ordinarily do this with kernel options and doesn''t
want to use a bootloader.
Sorry, I''m a bit sore on this :-)
Peace.
Andrew
On Tue, 2006-11-14 at 16:48 -0800, jdsw wrote:> Forwarding to devel list.
> (changed the wordings bit)
>
> The xmexample1 seems to contain
>
> hostname= "vm%d" % vmid
>
> Does this work with HVM ? I tried setting hostname=foo for my
> HVM based FC5 Linux domU. It does not seem to work.
>
> Also, is there a way to set IP address for a Linux HVM DomU ?
> I have seen somewhere (not in xen example)
> vif = [ ''ip=192.168.1.12'' ]
>
> How do both these work ? (if they are supposed to work )
> Are some scripts run after DomU is instantiated ? OR are
> passed as kernel params ?
>
> Thanks
> /Jd
> ps. anyone using these params, can u please send me output of
> cat /proc/cmdline
> from DomU
>
>
>
>
> ______________________________________________________________
> Cheap Talk? Check out Yahoo! Messenger''s low PC-to-Phone
call
> rates.
>
>
>
>
> ______________________________________________________________________
> Check out the all-new Yahoo! Mail beta - Fire up a more powerful email
> and get things done faster.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
> I strongly dislike the {ip, dhcp, root*} options. They map > to Linux kernel options. If someone wants to do that in the > configuration instead of a bootloader configuration, I think > the should use the ill-named ''extra'' option, which is > appended to the kernel command line. > This is for paravirtualized linux domU''s. > > Would be best if ip configuration is done in userspace of the > guest unless someone would ordinarily do this with kernel > options and doesn''t want to use a bootloader.Yep, I''d like to see these disappear when we move to the new config file format. Should we wish to provide convenience functions for the linux kernel command line ip pnp config they should be called cmdline_linux_ip_addr etc. Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Looking at the response, it seems that these (ip,netmask, hostname etc) end up as kernel cmdline parameters. does vif = [ ''ip=192.168.0.12'' ] also end up in kernel parameter similar to ip = ''192.168.0.12'' ? Thanks /Jd Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:> I strongly dislike the {ip, dhcp, root*} options. They map > to Linux kernel options. If someone wants to do that in the > configuration instead of a bootloader configuration, I think > the should use the ill-named ''extra'' option, which is > appended to the kernel command line. > This is for paravirtualized linux domU''s. > > Would be best if ip configuration is done in userspace of the > guest unless someone would ordinarily do this with kernel > options and doesn''t want to use a bootloader.Yep, I''d like to see these disappear when we move to the new config file format. Should we wish to provide convenience functions for the linux kernel command line ip pnp config they should be called cmdline_linux_ip_addr etc. Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --------------------------------- Sponsored Link $420,000 Mortgage for $1,399/month - Think You Pay Too Much For Your Mortgage? Find Out! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel