thing is the generated pxelinux.cfg entry looks like the below
append initrd=/images/Xen-Enterprise-5.0.0/xen.gz ksdevice=eth0
lang= console=com1,tty console=tty0 console=ttyS0,115200n8
com1=115200,8n1 text ---=None ---=None
answerfile=http://10.160.200.21/xenserver-5.0.0/10.160.201.116-answerfile
install watchdog ramdisk_size=32758 root=/dev/ram0
Xen-Enterprise-5.0.0/vmlinuz Xen-Enterprise-5.0.0/install.img
ks=http://192.168.11.1/cblr/svc/op/ks/system/testbox
in that the order of how the line is laid out is different and also
there are some options added by default such as the ks location and text.
(1) Presently kernel options in cobbler are a hash and do not preserve
order.
(2) ks location shouldn't be set if the kickstart is blank. You've
probably set it so there is a kickstart file installed.
(3) text and other parameters are set by /etc/cobbler/settings so you
can not have those added by default
(4) your usage of answerfile seems to imply this would be best treated
as another cobbler breed, though we don't want
to that just for XenEnt really
====
This would seem to defeat the "overriding kernel arguments" features of
cobbler if we stored them as something
other than a hash and we haven't had a need for this before now really.
Is this a problem with the multiple console lines being out of order or
something else?