Re: [Xen-API] How to create Templates for Network Installs that need additional Kernel-parameters ?? eliloader.py - patch suggestion

[Grant McWilliams <grantmasterflash@xxxxxxxxx>]

On Mon, Nov 5, 2012 at 8:38 AM, Andreas Balg <a.balg@xxxxxxxx> wrote:

Hello everybody,

I just tried to get a hands off auto-installation-template up and running on XCP 1.6(still beta1)Â - But I'm wondering how I might pass those basic extra arguments to the installer-image using eliloader

e.g. in pxeconf I'd say something like:

ÂÂÂÂÂÂÂ KERNEL installer/centos/6/i386/vmlinuz
ÂÂÂÂÂÂÂ APPEND initrd=installer/centos/6/i386/initrd.img ip=dhcp ksdevice=eth0 noipv6 ks=http://mirror.ournet.com/clavis/kickstart/centos/6./i386/basesystem.cfg

I tried to stuff the Kickstart-parameters "ip=dhcp ksdevice=eth0 noipv6 ks=http://mirror.ournet.com/kickstart/centos/6.3/i386/basesystem.cfg" in PV-args of the Template - but as expected, for the first time the installer runs eliloader.py It does not seem to take those into account but replace it with it's autogenerated stuff.

Is thereÂanother way I do not understand how I am supposed to do this in XCP 1.6 or would I have to make something like the patch for eliloader.py below
introducing yet another "other-config" as I did in the experimenetal patch below (which works for me - but I'd rather prefer not to patch the hypervisor-scripts for my needs ...)

Why aren't you just putting the network information in the kickstart file? ÂI have several automated install tutorials for XCPÂhttp://grantmcwilliams.com/tech/virtualization/xcp-howtos

Grant McWilliams
http://grantmcwilliams.com/

Some people, when confronted with a problem, think "I know, I'll use Windows."Â
Now they have two problems.

Â

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api