VMware Cloud Community
zenivox
Hot Shot
Hot Shot

BOOT.CFG amendment does not work to automate ESXi install with KS.CFG file

Hello, if I press shift+o at boot and I enter:

ks=nfs://IP1/KS/KS.CFG ip=IP2 netmask=255.255.255.0 gateway=IP3 netdevice=vmnic0

it works fine. But when I set the line in boot.cfg it does not work. I also tried to save the ks.cfg file in the ISO file in all possible ways and consulted various forums and VMware KB and docs pages. Nothing, I always get the illegal opt code message. I tried:

kernelopt=runweasel ks=cdrom:/KS.CFG

kernelopt=ks=cdrom:/KS.CFG

as well as the line at the beginning which works manually. I'm on HP BL g8. Any hint anyone?

Reply
0 Kudos
6 Replies
ThompsG
Virtuoso
Virtuoso

Hi zenivox,

Could I be rude and ask that you upload the boot.cfg file that doesn't work to this thread?

Kind regards.

Reply
0 Kudos
ThompsG
Virtuoso
Virtuoso

Also could you post the message (screenshot if possible) of the error that you get when incorporating the KS.CFG file into the CDROM image?

Kind regards.

Reply
0 Kudos
zenivox
Hot Shot
Hot Shot

Hello ThompsG, you are not being rude at all and thanks for helping... here's the boot.cfg content:

bootstate=0

title=Loading ESXi installer

timeout=5

prefix=

kernel=/tboot.b00

kernelopt=ks=cdrom:/KS.CFG

modules=/b.b00 --- /jumpstrt.gz --- /useropts.gz --- /features.gz --- /k.b00 --- /chardevs.b00 --- /a.b00 --- /user.b00 --- /uc_intel.b00 --- /uc_amd.b00 --- /sb.v00 --- /s.v00 --- /scsi_mpt.v00 --- /elx_esx_.v00 --- /elxiscsi.v00 --- /elxnet.v00 --- /lpfc.v00 --- /amshelpe.v00 --- /conrep.v00 --- /hpbootcf.v00 --- /hpe_buil.v00 --- /hpe_cru.v00 --- /hpe_esxi.v00 --- /hpe_ilo.v00 --- /hpe_nmi.v00 --- /hpe_smx_.v00 --- /hponcfg.v00 --- /hptestev.v00 --- /scsi_hpd.v00 --- /scsi_hpv.v00 --- /ssacli.v00 --- /nhpsa.v00 --- /qedentv.v00 --- /qfle3.v00 --- /misc_cni.v00 --- /net_bnx2.v00 --- /net_bnx2.v01 --- /net_cnic.v00 --- /qlnative.v00 --- /scsi_bnx.v00 --- /scsi_bnx.v01 --- /ata_liba.v00 --- /ata_pata.v00 --- /ata_pata.v01 --- /ata_pata.v02 --- /ata_pata.v03 --- /ata_pata.v04 --- /ata_pata.v05 --- /ata_pata.v06 --- /ata_pata.v07 --- /block_cc.v00 --- /bnxtnet.v00 --- /char_ran.v00 --- /ehci_ehc.v00 --- /hid_hid.v00 --- /i40en.v00 --- /igbn.v00 --- /ima_qla4.v00 --- /ipmi_ipm.v00 --- /ipmi_ipm.v01 --- /ipmi_ipm.v02 --- /ixgben.v00 --- /lsi_mr3.v00 --- /lsi_msgp.v00 --- /lsi_msgp.v01 --- /misc_dri.v00 --- /mtip32xx.v00 --- /ne1000.v00 --- /nenic.v00 --- /net_cdc_.v00 --- /net_e100.v00 --- /net_e100.v01 --- /net_enic.v00 --- /net_fcoe.v00 --- /net_forc.v00 --- /net_igb.v00 --- /net_ixgb.v00 --- /net_libf.v00 --- /net_mlx4.v00 --- /net_mlx4.v01 --- /net_nx_n.v00 --- /net_tg3.v00 --- /net_usbn.v00 --- /net_vmxn.v00 --- /nmlx4_co.v00 --- /nmlx4_en.v00 --- /nmlx4_rd.v00 --- /nmlx5_co.v00 --- /ntg3.v00 --- /nvme.v00 --- /nvmxnet3.v00 --- /ohci_usb.v00 --- /pvscsi.v00 --- /qflge.v00 --- /sata_ahc.v00 --- /sata_ata.v00 --- /sata_sat.v00 --- /sata_sat.v01 --- /sata_sat.v02 --- /sata_sat.v03 --- /sata_sat.v04 --- /scsi_aac.v00 --- /scsi_adp.v00 --- /scsi_aic.v00 --- /scsi_fni.v00 --- /scsi_ips.v00 --- /scsi_isc.v00 --- /scsi_lib.v00 --- /scsi_meg.v00 --- /scsi_meg.v01 --- /scsi_meg.v02 --- /scsi_mpt.v01 --- /scsi_mpt.v02 --- /scsi_qla.v00 --- /shim_isc.v00 --- /shim_isc.v01 --- /shim_lib.v00 --- /shim_lib.v01 --- /shim_lib.v02 --- /shim_lib.v03 --- /shim_lib.v04 --- /shim_lib.v05 --- /shim_vmk.v00 --- /shim_vmk.v01 --- /shim_vmk.v02 --- /smartpqi.v00 --- /uhci_usb.v00 --- /usb_stor.v00 --- /usbcore_.v00 --- /vmkata.v00 --- /vmkplexe.v00 --- /vmkusb.v00 --- /vmw_ahci.v00 --- /xhci_xhc.v00 --- /emulex_e.v00 --- /btldr.t00 --- /weaselin.t00 --- /esx_dvfi.v00 --- /esx_ui.v00 --- /lsu_hp_h.v00 --- /lsu_lsi_.v00 --- /lsu_lsi_.v01 --- /lsu_lsi_.v02 --- /lsu_lsi_.v03 --- /native_m.v00 --- /rste.v00 --- /vmware_e.v00 --- /vsan.v00 --- /vsanheal.v00 --- /vsanmgmt.v00 --- /tools.t00 --- /xorg.v00 --- /imgdb.tgz --- /imgpayld.tgz

build=

updated=0

let me run it again and I will attach the error message.. give me some time

Reply
0 Kudos
zenivox
Hot Shot
Hot Shot

RSOD.PNG

there you go...

Reply
0 Kudos
ThompsG
Virtuoso
Virtuoso

Hi there,

I've used your ks.cfg file and don't get the message - small comfort to yourself but at least the file appears to be okay.

Looking at the message it appears this could be caused by wrong boot order. Can you check here and see if this applies (assuming you haven't already done this):

Also can you check the ILO and BIOS version to make sure you are running the current version of both?

Hopefully this helps and doesn't hurt Smiley Wink

Reply
0 Kudos
zenivox
Hot Shot
Hot Shot

Many thanks for yout time! I went through those links and they didn't help in my case. Boot order in the bios is set to cdrom correctly. Thanks for ttrying my KS file, really appreciated...at least I know it's purely a HP thing now..

Reply
0 Kudos