Hi Mike,
Are you running the latest cobbler: 2.4.2?
Here’s my distro report from a working 5.0 U3 distro:
[root@foo cobbler]# cobbler distro report --name=esxi5.0-u3-ga-x86_64
Name : esxi5.0-u3-ga-x86_64
Architecture : x86_64
TFTP Boot Files : {'$local_img_path/*.*': '/var/www/cobbler/ks_mirror/esxi5.0-u3-ga/*.*'}
Breed : vmware
Comment :
Fetchable Files : {}
Initrd : /var/www/cobbler/ks_mirror/esxi5.0-u3-ga/imgpayld.tgz
Kernel : /var/www/cobbler/ks_mirror/esxi5.0-u3-ga/mboot.c32
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree': 'http://@@http_server@@/cblr/links/esxi5.0-u3-ga-x86_64'}
Management Classes : []
OS Version : esxi5
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {'/etc/cobbler/pxe/bootcfg_esxi5.template': '$local_img_path/cobbler-boot.cfg'}
In actuality, boot.cfg shouldn’t be used, the “cobbler-boot.cfg” should be built from template and used instead. I’ve noticed that this file isn’t automagically created
after the import operation and I have to run a sync after the import to have it be generated properly.
Also, if you’ve injected any drivers/software into the ESXi 5.x image, the correct modules list won’t be properly pulled into the cobbler-boot.cfg file… this is because
the bootcfg_esxi5.template file has a hard-coded list of default modules. I submitted a fix for this that was pulled into master, but I don’t think it’s yet gone into a release… perhaps in 2.4.3 …
Andy
From: cobbler-bounces@lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org]
On Behalf Of Outland, Mike
Sent: Thursday, February 20, 2014 8:13 PM
To: cobbler@lists.fedorahosted.org
Subject: [cobbler] Help with Cobbler 2.4 and ESXi 5
Hello,
I’m trying to get cobbler to use ESXi 5. I’m getting this error when I try and boot.
“Configuration error while parsing /boot.cfg
Fatal error: 15 (Not Found)”
I see this in my /var/log/messages:
Feb 20 16:54:55 cobbler in.tftpd[11477]: RRQ from 10.21.111.211 filename /pxelinux.0
Feb 20 16:54:55 cobbler in.tftpd[11479]: RRQ from 10.21.111.211 filename /pxelinux.cfg/40867f18-bb4b-df11-93ef-8843e1c2b2e8
Feb 20 16:54:55 cobbler in.tftpd[11480]: RRQ from 10.21.111.211 filename /pxelinux.cfg/01-88-43-e1-c2-b2-ee
Feb 20 16:54:55 cobbler in.tftpd[11481]: RRQ from 10.21.111.211 filename //images/ESX-5.0-x86_64/mboot.c32
Feb 20 16:54:57 cobbler in.tftpd[11482]: RRQ from 10.21.111.211 filename //boot.cfg
I don’t see any boot.cfg in /var/lib/tftpboot directory. I’m not sure why there are two slashes there.
Here is my cobbler distro report:
Name : ESX-5.0-x86_64
Architecture : x86_64
TFTP Boot Files : {}
Breed : vmware
Comment :
Fetchable Files : {}
Initrd : /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/imgpayld.tgz
Kernel : /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree': 'http://@@http_server@@/cblr/ks_mirror/ESX-5.0-x86_64'}
Management Classes : []
OS Version : esxi5
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
I’ve seen some people populate TFTP Boot Files or Fetchable Files, but I can’t seem to find out what should be there, if anything?
And what tells the system to fetch this boot.cfg file? I see one in my /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/boot.cfg
[root@cobbler /]# cat var/www/cobbler/ks_mirror/ESX-5.0-x86_64/boot.cfg
bootstate=0
title=Loading ESXi installer
kernel=/tboot.b00
kernelopt=runweasel
modules=/b.b00 --- /useropts.gz --- /k.b00 --- /a.b00 --- /misc-cni.v00 --- /net-bnx2.v00 --- /net-cnic.v00 --- /net-tg3.v00 --- /scsi-bnx.v00
--- /scsi-bnx.v01 --- /net-enic.v00 --- /scsi-fni.v00 --- /net-be2n.v00 --- /scsi-lpf.v00 --- /net-igb.v00 --- /net-ixgb.v00 --- /net-qlcn.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 --- /ehci-ehc.v00 --- /s.v00 --- /weaselin.i00 --- /ima-qla4.v00 --- /ipmi-ipm.v00 --- /ipmi-ipm.v01 --- /ipmi-ipm.v02 --- /misc-dri.v00 --- /net-bnx2.v01 --- /net-e100.v00 --- /net-e100.v01 --- /net-forc.v00 --- /net-nx-n.v00
--- /net-qlge.v00 --- /net-r816.v00 --- /net-r816.v01 --- /net-s2io.v00 --- /net-sky2.v00 --- /ohci-usb.v00 --- /sata-ahc.v00 --- /sata-ata.v00 --- /sata-sat.v00 --- /sata-sat.v01 --- /sata-sat.v02 --- /sata-sat.v03 --- /scsi-aac.v00 --- /scsi-adp.v00 ---
/scsi-aic.v00 --- /scsi-hps.v00 --- /scsi-ips.v00 --- /scsi-meg.v00 --- /scsi-meg.v01 --- /scsi-meg.v02 --- /scsi-mpt.v00 --- /scsi-mpt.v01 --- /scsi-mpt.v02 --- /scsi-qla.v00 --- /scsi-qla.v01 --- /scsi-rst.v00 --- /uhci-usb.v00 --- /tools.t00 --- /imgdb.tgz
--- /imgpayld.tgz
build=
updated=0
I appreciate your help.
Thanks,
-mike
Mike Outland
DevOps Manager
Single Number Reach: 925-226-3360 Fax: 925-226-3335
Collaboration 
Data
Center Borderless
Networks
Business Video
Managed Services.
Nexus IS Inc. designs, builds and supports complete end-to
end technology solutions designed to help organizations
Connect to their customers, Collaborate to achieve
their
vision, and Create innovative solutions to business
problems.
The information contained in this email and any additional
attachments is confidential and may be legally privileged. If you
are not the intended recipient then you must not use, disseminate,
distribute or copy any information contained in this email or any
attachments. If you receive this email in error, please destroy it
immediately and contact us. Thank you.