8:12 p.m.
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
[cid:FD6171CC-E24F-4CF6-8AED-64987831ADE1]
Single Number Reach: 925-226-3360 Fax: 925-226-3335
mike.outland@nexusis.com<mailto:mike.outland@nexusis.com>
www.nexusis.com<http://www.nexusis.com/>
Collaboration [cid:3C493362-4A32-4445-BD51-0F110316CA5D] Data Center
[cid:96D28F55-6D6A-48B0-8291-FC40F916AB41] Borderless Networks
[cid:E8E8FB68-069C-4EF8-98A9-C6C58D149BAA]
Business Video [cid:C8A8D6D5-7B14-45A2-B4F4-7B95963544A3]
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.
[cid:D448E73D-5290-4762-A950-C1E32BD70CA7][cid:E3A60D0C-EF5F-4F36-86AD-30ECE1043452][cid:1469119F-1072-423F-86BB-12EEC84B8D48][cid:FA9B9376-7116-43D1-A448-506E3EC58431]
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.
7:30 a.m.
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(a)lists.fedorahosted.org
[mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Outland, Mike
Sent: Thursday, February 20, 2014 8:13 PM
To: cobbler(a)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
[cid:image001.png@01CF2ED6.42EF1EC0]
Single Number Reach: 925-226-3360 Fax: 925-226-3335
mike.outland@nexusis.com<mailto:mike.outland@nexusis.com>
www.nexusis.com<http://www.nexusis.com/>
Collaboration [cid:image002.png@01CF2ED6.42EF1EC0] Data Center
[cid:image002.png@01CF2ED6.42EF1EC0] Borderless Networks
[cid:image002.png@01CF2ED6.42EF1EC0]
Business Video [cid:image002.png@01CF2ED6.42EF1EC0]
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.
[cid:image003.png@01CF2ED6.42EF1EC0][cid:image004.png@01CF2ED6.42EF1EC0][cid:image005.png@01CF2ED6.42EF1EC0][cid:image006.png@01CF2ED6.42EF1EC0]
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.
7:47 a.m.
If this behaviour is annoying enough for vmware users i will cherry-pick
that change into release24, there will a new 2.4.3 release in a few weeks.
On Fri, Feb 21, 2014 at 2:30 PM, Speagle , Andy <Andy.Speagle(a)netapp.com>wrote:
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(a)lists.fedorahosted.org [mailto:
cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Outland, Mike
*Sent:* Thursday, February 20, 2014 8:13 PM
*To:* cobbler(a)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*
*mike.outland(a)nexusis.com <mike.outland(a)nexusis.com>*
*www.nexusis.com* <http://www.nexusis.com/>
*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.*
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
--
Grtz,
Jörgen Maas
12:39 p.m.
Hi Andy,
I’m using Cobbler 2.4.0 since 2.4.2 is not yet in EPEL and we use puppet for managing our
cobbler server.
I’ll try making my distro look like yours. I appreciate the help!
-mike
1:17 p.m.
I’m still seeing the same error at boot up.
Here is my distro as it is now.
Name : ESX-5.0-x86_64
Architecture : x86_64
TFTP Boot Files : {'$img_path/*.*':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/*.*'}
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 : {'/etc/cobbler/pxe/bootcfg_esxi5.template':
'$local_img_path/cobbler-boot.cfg'}
I have noticed this after running cobbler sync.
failed to copy file /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
And I’m suspecting that all files from /var/www.cobbler/ks_mirror/ESX-5.0-x86_64 should
end up in the /var/lib/tftpboot/images/ESX-5.0-x86_64/ ? I’m only seeing these files
there.
[root@cobbler ESX-5.0-x86_64]# ls -l
total 2852
-rw-r--r--. 1 root root 1279 Feb 21 11:09 cobbler-boot.cfg
-rw-r--r--. 2 root root 2833098 Feb 21 11:09 imgpayld.tgz
-rw-r--r--. 2 root root 80008 Feb 21 11:09 mboot.c32
[root@cobbler ESX-5.0-x86_64]# pwd
/var/lib/tftpboot/images/ESX-5.0-x86_64
And for some reason it is still searching for /boot.cfg and not the cobbler-boot.cfg.
Where is this controlled at?
Feb 21 11:12:34 cobbler in.tftpd[17198]: RRQ from 10.21.111.211 filename
/pxelinux.cfg/40867f18-bb4b-df11-93ef-8843e1c2b2e8
Feb 21 11:12:34 cobbler in.tftpd[17199]: RRQ from 10.21.111.211 filename
/pxelinux.cfg/01-88-43-e1-c2-b2-ee
Feb 21 11:12:34 cobbler in.tftpd[17200]: RRQ from 10.21.111.211 filename
//images/ESX-5.0-x86_64/mboot.c32
Feb 21 11:12:35 cobbler in.tftpd[17201]: RRQ from 10.21.111.211 filename //boot.cfg
1:28 p.m.
You might consider pulling release-24 from github and building some fresh RPMs via
"make rpms" ...
Andy
From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Outland, Mike
Sent: Friday, February 21, 2014 1:17 PM
To: cobbler mailing list
Subject: Re: [cobbler] Help with Cobbler 2.4 and ESXi 5
I'm still seeing the same error at boot up.
Here is my distro as it is now.
Name : ESX-5.0-x86_64
Architecture : x86_64
TFTP Boot Files : {'$img_path/*.*':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/*.*'}
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 : {'/etc/cobbler/pxe/bootcfg_esxi5.template':
'$local_img_path/cobbler-boot.cfg'}
I have noticed this after running cobbler sync.
failed to copy file /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
And I'm suspecting that all files from /var/www.cobbler/ks_mirror/ESX-5.0-x86_64
should end up in the /var/lib/tftpboot/images/ESX-5.0-x86_64/ ? I'm only seeing these
files there.
[root@cobbler ESX-5.0-x86_64]# ls -l
total 2852
-rw-r--r--. 1 root root 1279 Feb 21 11:09 cobbler-boot.cfg
-rw-r--r--. 2 root root 2833098 Feb 21 11:09 imgpayld.tgz
-rw-r--r--. 2 root root 80008 Feb 21 11:09 mboot.c32
[root@cobbler ESX-5.0-x86_64]# pwd
/var/lib/tftpboot/images/ESX-5.0-x86_64
And for some reason it is still searching for /boot.cfg and not the cobbler-boot.cfg.
Where is this controlled at?
Feb 21 11:12:34 cobbler in.tftpd[17198]: RRQ from 10.21.111.211 filename
/pxelinux.cfg/40867f18-bb4b-df11-93ef-8843e1c2b2e8
Feb 21 11:12:34 cobbler in.tftpd[17199]: RRQ from 10.21.111.211 filename
/pxelinux.cfg/01-88-43-e1-c2-b2-ee
Feb 21 11:12:34 cobbler in.tftpd[17200]: RRQ from 10.21.111.211 filename
//images/ESX-5.0-x86_64/mboot.c32
Feb 21 11:12:35 cobbler in.tftpd[17201]: RRQ from 10.21.111.211 filename //boot.cfg
2:57 p.m.
I get the exact same behavior in release24 branch. Still looking for //boot.cfg. How do
I tell it to look for this cobbler-boot.cfg instead? Also, shouldn’t it be trying to pull
/images/ESX-5.0-x86_64/cobbler-boot.cfg anyways? Mine seems to try for only //boot.cfg.
Where is this configured?
10:04 a.m.
Hey Mike,
I just merged Andy's work into the release24 branch.
Can you git pull and do another test please?
Thanks!
On Fri, Feb 21, 2014 at 9:57 PM, Outland, Mike <Mike.Outland(a)nexusis.com>wrote:
I get the exact same behavior in release24 branch. Still looking
for
//boot.cfg. How do I tell it to look for this cobbler-boot.cfg instead?
Also, shouldn't it be trying to pull
/images/ESX-5.0-x86_64/cobbler-boot.cfg anyways? Mine seems to try for
only //boot.cfg. Where is this configured?
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
--
Grtz,
Jörgen Maas
3:40 p.m.
Tried again, same result.
Still searching for /boot.cfg
Is anyone else able to replicate this problem I’m having?
Thanks,
-mike
3:52 p.m.
I do not have this. Here is my /etc/xinet*
[root@cobbler etc]# ls xinetd.*
xinetd.conf
xinetd.d:
chargen-dgram chargen-stream daytime-dgram daytime-stream discard-dgram
discard-stream echo-dgram echo-stream rsync tcpmux-server tftp time-dgram
time-stream
I checked file /etc/xinetd.d/tftp since that seems to be the closest to your question and
does have a server_args:
# default: off
# description: The tftp server serves files using the trivial file transfer \
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware printers, \
# and to start the installation process for some operating systems.
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -B 1380 -v -s /var/lib/tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}
6:32 p.m.
And what is in /var/lib/tftpboot?
is there a boot.cfg?
If not try putting on there and see if the error changes.
Regards,
Petro.
:wq
On 14/2/24 2:52 PM, Outland, Mike wrote:
I do not have this. Here is my /etc/xinet*
[root@cobbler etc]# ls xinetd.*
xinetd.conf
xinetd.d:
chargen-dgram chargen-stream daytime-dgram daytime-stream discard-dgram
discard-stream echo-dgram echo-stream rsync tcpmux-server tftp time-dgram
time-stream
I checked file /etc/xinetd.d/tftp since that seems to be the closest to your question and
does have a server_args:
# default: off
# description: The tftp server serves files using the trivial file transfer \
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware printers, \
# and to start the installation process for some operating systems.
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -B 1380 -v -s /var/lib/tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
12:29 p.m.
Ok,
I moved the boot.cfg that gets generated from /var/lib/tftpboot/images/ESX-5.0-x86_64/ to
the root /var/lib/tftpboot/ and I get a new error of:
/images/ESX-5.0-x86_64/tboot.b00: file not found.
The only files I have in the images directory are:
[root@cobbler ESX-5.0-x86_64]# ls -l
total 2852
-rw-r--r--. 1 root root 1340 Feb 24 13:34 boot.cfg
-rw-r--r--. 2 root root 2833098 Feb 24 13:33 imgpayld.tgz
-rw-r--r--. 2 root root 80008 Feb 24 13:33 mboot.c32
Even though I have this in my distro:
TFTP Boot Files : {'$img_path/*.*':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/*.*'}
However, I suspect this portion is actually failing because when I run cobbler sync I see
this error and I think it just quits the copy from here:
processing boot_files for distro: ESX-5.0-x86_64
failed to copy file /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
Any idea on the following?
1.) Tell the system to look for the boot.cfg in the images/ESX-5.0-x86_64 directory
instead of root?
2.) Get the system to copy all necessary boot files to the images/ESX-5.0-x86_64
directory
I appreciate everyones help here, I feel like I’m finally getting somewhere…
-mike
1:04 p.m.
What is happening is that the -s /var/lib/tftpboot bit in
/etc/inetd.d/tftp is telling in.tftpd (or tftpd depending on your
system) to "chroot" to /var/lib/tftpboot.
Anything you want tftpd to see will need to be under that directory.
Alternatively you could change the bits after the -s to point where you
want them.
My tendency is to prefer to leave the stuff in /etc/ alone as it's owned
by RPMs and upgrades can undo work if you're not careful.
My choice would be to create the directory paths under
/var/lib/tftpboot. Your life, your choice :)
Regards,
Petro.
:wq
On 14/2/25 11:29 AM, Outland, Mike wrote:
Ok,
I moved the boot.cfg that gets generated from
/var/lib/tftpboot/images/ESX-5.0-x86_64/ to the root
/var/lib/tftpboot/ and I get a new error of:
/images/ESX-5.0-x86_64/tboot.b00: file not found.
The only files I have in the images directory are:
[root@cobbler ESX-5.0-x86_64]# ls -l
total 2852
-rw-r--r--. 1 root root 1340 Feb 24 13:34 boot.cfg
-rw-r--r--. 2 root root 2833098 Feb 24 13:33 imgpayld.tgz
-rw-r--r--. 2 root root 80008 Feb 24 13:33 mboot.c32
Even though I have this in my distro:
TFTP Boot Files : {'$img_path/*.*':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/*.*'}
However, I suspect this portion is actually failing because when I run
cobbler sync I see this error and I think it just quits the copy from
here:
processing boot_files for distro: ESX-5.0-x86_64
failed to copy file
/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
Any idea on the following?
1.) Tell the system to look for the boot.cfg in the
images/ESX-5.0-x86_64 directory instead of root?
2.) Get the system to copy all necessary boot files to the
images/ESX-5.0-x86_64 directory
I appreciate everyones help here, I feel like I’m finally getting
somewhere…
-mike
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
1:27 p.m.
Petro,
Thank you for the quick response.
I’m wondering why this is the case. I am only using the default options for tftp and
cobbler in this regard. Something must be instructing the system to look for /boot.cfg
instead of /images/ESX-5.0-x86_64/. Why would the cobbler templates not generate the
boot.cfg in the proper location if it is infact in the tftpboot directory and not in the
distro directory? I would imagine if you had more than one ESX distro you would then have
collisions on the boot.cfg. I think something else is at play here.
Also how do I get the system to properly copy all the boot files to the tftp directory
when running cobbler sync?
-mike
2:22 p.m.
On 14/2/25 12:27 PM, Outland, Mike wrote:
Petro,
Thank you for the quick response.
I’m wondering why this is the case. I am only using the default options for tftp and
cobbler in this regard. Something must be instructing the system to look for /boot.cfg
instead of /images/ESX-5.0-x86_64/.
I can't really answer that, sorry. It's
been a *long* time since I've
been that deep in PXE booting/TFTP, and I haven't done cobbler with
TFTP, and I haven't used either for ESX.
I suspect that something in the ESX process is looking for the boot.cfg.
My best guess is something in menu.
This might help:
http://www.routereflector.com/2014/01/unattended-vmware-esxi-installation...
Note these bits in particular:
# cat /mnt/boot.cfg | sed -e "s#/##g" -e
"3s#^#prefix=esxi-5.1.0u1-1065491\n#" >
/tftpboot/pxe/esxi-5.1.0u1-1065491/boot.cfg
and
# vi /tftpboot/pxe/pxelinux.cfg/default
default menu.c32
prompt0
timeout300
menu title PXEBoot Menu
labellocal
menu label^0 - Boot from first hard drive
com32 chain.c32
append hd0
label1
menu label^1 - Install VMware ESXi 5.1.0u1
* kernel esxi**-**5.1**.**0u1**-**1065491**/**mboot**.**c32
append**-**c esxi**-**5.1**.**0u1**-**1065491**/**boot**.**cfg
ks**=**http**:**//172.31.30.1/ks/esxi-5.1.0u1.cfg*
Why would the cobbler templates not generate the boot.cfg in the
proper location if it is infact in the tftpboot directory and not in the distro directory?
I would imagine if you had more than one ESX distro you would then have collisions on the
boot.cfg. I think something else is at play here.
Also how do I get the system to properly copy all the boot files to the tftp directory
when running cobbler sync?
What happens right now when you run cobbler sync?
The top few lines of my output are:
task started: 2014-02-25_132124_sync
task started (id=Sync, time=Tue Feb 25 13:21:24 2014)
running pre-sync triggers
cleaning trees
removing: /var/lib/tftpboot/pxelinux.cfg/default
removing: /var/lib/tftpboot/grub/efidefault
removing: /var/lib/tftpboot/grub/images
removing: /var/lib/tftpboot/s390x/profile_list
copying bootloaders
copying: /usr/share/syslinux/pxelinux.0 -> /var/lib/tftpboot/pxelinux.0
copying: /usr/share/syslinux/menu.c32 -> /var/lib/tftpboot/menu.c32
copying: /usr/share/syslinux/memdisk -> /var/lib/tftpboot/memdisk
copying distros
copying images
But this is a non-production "I'm just playing with it" environment that
I started setting up last week, so I haven't really dug into it yet, and
since my soon to be future employer doesn't use it, it might get blown
away.
Regards,
Petro.
:wq
5:14 p.m.
I’m not using menu, I’m using a file generated by Cobbler which is the MAC of the system
which is PXE booting. Here are the contents of that file.
[root@cobbler pxelinux.cfg]# cat 01-88-43-e1-c2-b2-ee
default linux
prompt 0
timeout 1
label linux
kernel /images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append /images/ESX-5.0-x86_64/vmkboot.gz BOOTIF=01-88-43-e1-c2-b2-ee
ks=http://10.21.111.195/cblr/svc/op/ks/system/devops1 lang= text ---
/images/ESX-5.0-x86_64/vmkernel.gz --- /images/ESX-5.0-x86_64/sys.vgz ---
/images/ESX-5.0-x86_64/cim.vgz --- /images/ESX-5.0-x86_64/ienviron.vgz ---
/images/ESX-5.0-x86_64/install.vgz
I even tried adding the line:
append -c /images/ESX-5.0-x86_64/boot.cfg
Which made no difference, still searching for //boot.cfg.
This is what I’m seeing while running cobbler sync, towards the end of the run.
processing boot_files for distro: ESX-5.0-x86_64
failed to copy file /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
On Feb 25, 2014, at 12:22 PM, Petro <petro@cpetro.us<mailto:petro@cpetro.us>>
wrote:
On 14/2/25 12:27 PM, Outland, Mike wrote:
Petro,
Thank you for the quick response.
I’m wondering why this is the case. I am only using the default options for tftp and
cobbler in this regard. Something must be instructing the system to look for /boot.cfg
instead of /images/ESX-5.0-x86_64/.
I can't really answer that, sorry. It's been a *long* time since I've been
that deep in PXE booting/TFTP, and I haven't done cobbler with TFTP, and I haven't
used either for ESX.
I suspect that something in the ESX process is looking for the boot.cfg. My best guess is
something in menu.
This might help:
http://www.routereflector.com/2014/01/unattended-vmware-esxi-installation...
Note these bits in particular:
# cat /mnt/boot.cfg | sed -e "s#/##g" -e
"3s#^#prefix=esxi-5.1.0u1-1065491\n#" >
/tftpboot/pxe/esxi-5.1.0u1-1065491/boot.cfg
and
# vi /tftpboot/pxe/pxelinux.cfg/default
default menu.c32
prompt 0
timeout 300
menu title PXE Boot Menu
label local
menu label ^0 - Boot from first hard drive
com32 chain.c32
append hd0
label 1
menu label ^1 - Install VMware ESXi 5.1.0u1
kernel esxi-5.1.0u1-1065491/mboot.c32
append -c esxi-5.1.0u1-1065491/boot.cfg ks=http://172.31.30.1/ks/esxi-5.1.0u1.cfg
Why would the cobbler templates not generate the boot.cfg in the proper location if it is
infact in the tftpboot directory and not in the distro directory? I would imagine if you
had more than one ESX distro you would then have collisions on the boot.cfg. I think
something else is at play here.
Also how do I get the system to properly copy all the boot files to the tftp directory
when running cobbler sync?
What happens right now when you run cobbler sync?
The top few lines of my output are:
task started: 2014-02-25_132124_sync
task started (id=Sync, time=Tue Feb 25 13:21:24 2014)
running pre-sync triggers
cleaning trees
removing: /var/lib/tftpboot/pxelinux.cfg/default
removing: /var/lib/tftpboot/grub/efidefault
removing: /var/lib/tftpboot/grub/images
removing: /var/lib/tftpboot/s390x/profile_list
copying bootloaders
copying: /usr/share/syslinux/pxelinux.0 -> /var/lib/tftpboot/pxelinux.0
copying: /usr/share/syslinux/menu.c32 -> /var/lib/tftpboot/menu.c32
copying: /usr/share/syslinux/memdisk -> /var/lib/tftpboot/memdisk
copying distros
copying images
But this is a non-production "I'm just playing with it" environment that I
started setting up last week, so I haven't really dug into it yet, and since my soon
to be future employer doesn't use it, it might get blown away.
Regards,
Petro.
:wq
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
8:15 p.m.
Just to see if it changes something try:
default linux
prompt 0
timeout 1
label linux
kernel images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append -c images/ESX-5.0-x86_64/boot.cfg
**just** that and see if it gets further.
Note also relative paths.
And make sure boot.cfg
On 14/2/25 4:14 PM, Outland, Mike wrote:
I’m not using menu, I’m using a file generated by Cobbler which is
the
MAC of the system which is PXE booting. Here are the contents of that
file.
[root@cobbler pxelinux.cfg]# cat 01-88-43-e1-c2-b2-ee
default linux
prompt 0
timeout 1
label linux
kernel /images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append /images/ESX-5.0-x86_64/vmkboot.gz
BOOTIF=01-88-43-e1-c2-b2-ee
ks=http://10.21.111.195/cblr/svc/op/ks/system/devops1 lang= text ---
/images/ESX-5.0-x86_64/vmkernel.gz --- /images/ESX-5.0-x86_64/sys.vgz
--- /images/ESX-5.0-x86_64/cim.vgz ---
/images/ESX-5.0-x86_64/ienviron.vgz --- /images/ESX-5.0-x86_64/install.vgz
I even tried adding the line:
append -c /images/ESX-5.0-x86_64/boot.cfg
Which made no difference, still searching for //boot.cfg.
This is what I’m seeing while running cobbler sync, towards the end of
the run.
processing boot_files for distro: ESX-5.0-x86_64
failed to copy file
/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
On Feb 25, 2014, at 12:22 PM, Petro <petro(a)cpetro.us
<mailto:petro@cpetro.us>> wrote:
> On 14/2/25 12:27 PM, Outland, Mike wrote:
>> Petro,
>> Thank you for the quick response.
>>
>> I’m wondering why this is the case. I am only using the default options for tftp
and cobbler in this regard. Something must be instructing the system to look for
/boot.cfg instead of /images/ESX-5.0-x86_64/.
> I can't really answer that, sorry. It's been a *long* time since I've
> been that deep in PXE booting/TFTP, and I haven't done cobbler with
> TFTP, and I haven't used either for ESX.
>
> I suspect that something in the ESX process is looking for the
> boot.cfg. My best guess is something in menu.
>
> This might help:
>
>
http://www.routereflector.com/2014/01/unattended-vmware-esxi-installation...
>
> Note these bits in particular:
> # cat /mnt/boot.cfg | sed -e "s#/##g" -e
"3s#^#prefix=esxi-5.1.0u1-1065491\n#" >
/tftpboot/pxe/esxi-5.1.0u1-1065491/boot.cfg
> and
>
> # vi /tftpboot/pxe/pxelinux.cfg/default
> default menu.c32
> prompt0
> timeout300
>
> menu title PXEBoot Menu
>
> labellocal
> menu label^0 - Boot from first hard drive
> com32 chain.c32
> append hd0
>
> label1
> menu label^1 - Install VMware ESXi 5.1.0u1
> * kernel esxi**-**5.1**.**0u1**-**1065491**/**mboot**.**c32
> append**-**c esxi**-**5.1**.**0u1**-**1065491**/**boot**.**cfg
ks**=**http**:**//172.31.30.1/ks/esxi-5.1.0u1.cfg*
>
>
>> Why would the cobbler templates not generate the boot.cfg in the proper location
if it is infact in the tftpboot directory and not in the distro directory? I would
imagine if you had more than one ESX distro you would then have collisions on the
boot.cfg. I think something else is at play here.
>>
>> Also how do I get the system to properly copy all the boot files to the tftp
directory when running cobbler sync?
>
> What happens right now when you run cobbler sync?
>
> The top few lines of my output are:
>
> task started: 2014-02-25_132124_sync
> task started (id=Sync, time=Tue Feb 25 13:21:24 2014)
> running pre-sync triggers
> cleaning trees
> removing: /var/lib/tftpboot/pxelinux.cfg/default
> removing: /var/lib/tftpboot/grub/efidefault
> removing: /var/lib/tftpboot/grub/images
> removing: /var/lib/tftpboot/s390x/profile_list
> copying bootloaders
> copying: /usr/share/syslinux/pxelinux.0 -> /var/lib/tftpboot/pxelinux.0
> copying: /usr/share/syslinux/menu.c32 -> /var/lib/tftpboot/menu.c32
> copying: /usr/share/syslinux/memdisk -> /var/lib/tftpboot/memdisk
> copying distros
> copying images
>
>
> But this is a non-production "I'm just playing with it" environment
> that I started setting up last week, so I haven't really dug into it
> yet, and since my soon to be future employer doesn't use it, it might
> get blown away.
>
> Regards,
> Petro.
> :wq
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org>
> https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
1:25 p.m.
Petro,
That did not change anything. I still can’t figure out where Cobbler is configure to tell
the system to look for /boot.cfg. If I can get past that, I can complete this task.
On a side note I was able to get this to work by a few manual steps.
1.) Copy the boot.cfg from the /var/lib/tftpboot/images/ESX-5.0-x86_64 directory to the
/var/lib/tftpboot
2.) Manually copy all files from /var/www/cobbler/ks_mirror/ESX-5.0-x86_64 to
/var/lib/tftpboot/images/ESX-5.0-x86_64
I think I can fix #2 by listing out each file explicitly in the TFTP_boot files for the
distro instead of asking for *.* which causes the copy failure on an existing file (kernel
and initrd specified in the distro).
However I have no idea how to really fix #1. :(
Just to see if it changes something try:
default linux
prompt 0
timeout 1
label linux
kernel images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append -c images/ESX-5.0-x86_64/boot.cfg
**just** that and see if it gets further.
Note also relative paths.
And make sure boot.cfg
On 14/2/25 4:14 PM, Outland, Mike wrote:
I’m not using menu, I’m using a file generated by Cobbler which is the MAC of the system
which is PXE booting. Here are the contents of that file.
[root@cobbler pxelinux.cfg]# cat 01-88-43-e1-c2-b2-ee
default linux
prompt 0
timeout 1
label linux
kernel /images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append /images/ESX-5.0-x86_64/vmkboot.gz BOOTIF=01-88-43-e1-c2-b2-ee
ks=http://10.21.111.195/cblr/svc/op/ks/system/devops1 lang= text ---
/images/ESX-5.0-x86_64/vmkernel.gz --- /images/ESX-5.0-x86_64/sys.vgz ---
/images/ESX-5.0-x86_64/cim.vgz --- /images/ESX-5.0-x86_64/ienviron.vgz ---
/images/ESX-5.0-x86_64/install.vgz
I even tried adding the line:
append -c /images/ESX-5.0-x86_64/boot.cfg
Which made no difference, still searching for //boot.cfg.
This is what I’m seeing while running cobbler sync, towards the end of the run.
processing boot_files for distro: ESX-5.0-x86_64
failed to copy file /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
On Feb 25, 2014, at 12:22 PM, Petro <petro@cpetro.us<mailto:petro@cpetro.us>>
wrote:
On 14/2/25 12:27 PM, Outland, Mike wrote:
Petro,
Thank you for the quick response.
I’m wondering why this is the case. I am only using the default options for tftp and
cobbler in this regard. Something must be instructing the system to look for /boot.cfg
instead of /images/ESX-5.0-x86_64/.
I can't really answer that, sorry. It's been a *long* time since I've been
that deep in PXE booting/TFTP, and I haven't done cobbler with TFTP, and I haven't
used either for ESX.
I suspect that something in the ESX process is looking for the boot.cfg. My best guess is
something in menu.
This might help:
http://www.routereflector.com/2014/01/unattended-vmware-esxi-installation...
Note these bits in particular:
# cat /mnt/boot.cfg | sed -e "s#/##g" -e
"3s#^#prefix=esxi-5.1.0u1-1065491\n#" >
/tftpboot/pxe/esxi-5.1.0u1-1065491/boot.cfg
and
# vi /tftpboot/pxe/pxelinux.cfg/default
default menu.c32
prompt 0
timeout 300
menu title PXE Boot Menu
label local
menu label ^0 - Boot from first hard drive
com32 chain.c32
append hd0
label 1
menu label ^1 - Install VMware ESXi 5.1.0u1
kernel esxi-5.1.0u1-1065491/mboot.c32
append -c esxi-5.1.0u1-1065491/boot.cfg ks=http://172.31.30.1/ks/esxi-5.1.0u1.cfg
Why would the cobbler templates not generate the boot.cfg in the proper location if it is
infact in the tftpboot directory and not in the distro directory? I would imagine if you
had more than one ESX distro you would then have collisions on the boot.cfg. I think
something else is at play here.
Also how do I get the system to properly copy all the boot files to the tftp directory
when running cobbler sync?
What happens right now when you run cobbler sync?
The top few lines of my output are:
task started: 2014-02-25_132124_sync
task started (id=Sync, time=Tue Feb 25 13:21:24 2014)
running pre-sync triggers
cleaning trees
removing: /var/lib/tftpboot/pxelinux.cfg/default
removing: /var/lib/tftpboot/grub/efidefault
removing: /var/lib/tftpboot/grub/images
removing: /var/lib/tftpboot/s390x/profile_list
copying bootloaders
copying: /usr/share/syslinux/pxelinux.0 -> /var/lib/tftpboot/pxelinux.0
copying: /usr/share/syslinux/menu.c32 -> /var/lib/tftpboot/menu.c32
copying: /usr/share/syslinux/memdisk -> /var/lib/tftpboot/memdisk
copying distros
copying images
But this is a non-production "I'm just playing with it" environment that I
started setting up last week, so I haven't really dug into it yet, and since my soon
to be future employer doesn't use it, it might get blown away.
Regards,
Petro.
:wq
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
2:44 p.m.
On 14/2/26 12:25 PM, Outland, Mike wrote:
Petro,
That did not change anything. I still can’t figure out where Cobbler
is configure to tell the system to look for /boot.cfg. If I can get
past that, I can complete this task.
There's at 4 different systems or packages interacting here. DHCP, TFTP,
PXE. My bet at this point is that Cobbler isn't doing anything (whether
it should or not I'm not sure. I think most of these files are outside
of cobbler control. The Cobbler Devs can certainly tell me I'm wrong).
This is from your first email (or at least the first email I've seen):
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
What happens here is that the pxeboot stuff on your physical host is
making a request for "pxelinux.0" which loads and runs. Pxelinux.0 then
starts making requests for
pxelinux.cfg/40867f18-bb4b-df11-93ef-8843e1c2b2e8 and then
pxelinux.cfg/01-88-43-e1-c2-b2-ee. It finds
pxelinux.cfg/01-88-43-e1-c2-b2-ee which is a configuration file which
originally had:
###
default linux
prompt 0
timeout 1
label linux
kernel /images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append /images/ESX-5.0-x86_64/vmkboot.gz
BOOTIF=01-88-43-e1-c2-b2-ee
ks=http://10.21.111.195/cblr/svc/op/ks/system/devops1 lang= text ---
/images/ESX-5.0-x86_64/vmkernel.gz --- /images/ESX-5.0-x86_64/sys.vgz
--- /images/ESX-5.0-x86_64/cim.vgz ---
/images/ESX-5.0-x86_64/ienviron.vgz --- /images/ESX-5.0-x86_64/install.vgz
###
When mboot.c32 runs it makes a request for "/boot.cfg". I suspect that
something in pxelinux.cfg/01-88-43-e1-c2-b2-ee isn't quite right and the
"-c images/ESX-5.0-x86_64/boot.cfg" isn't getting passed properly.
We changed the images/ESX-5.0-x86_64/boot.cfg file to look like:
default linux
prompt 0
timeout 1
label linux
kernel images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append -c images/ESX-5.0-x86_64/boot.cfg
right? But it's still looking for /boot.cfg.
What happens if you do:
label linux
kernel images/ESX-5.0-x86_64/mboot.c32
append -c images/ESX-5.0-x86_64/boot.cfg
And if that works, stick the ipappend 2 back in and see if that breaks
it again.
What does your DHCP config look like for this group?
On a side note I was able to get this to work by a few manual steps.
1.) Copy the boot.cfg from the
/var/lib/tftpboot/images/ESX-5.0-x86_64 directory to the /var/lib/tftpboot
Yeah,
that doesn't surprise me.
2.) Manually copy all files from
/var/www/cobbler/ks_mirror/ESX-5.0-x86_64
to /var/lib/tftpboot/images/ESX-5.0-x86_64
I think I can fix #2 by listing out each file explicitly in the
TFTP_boot files for the distro instead of asking for *.* which causes
the copy failure on an existing file (kernel and initrd specified in
the distro).
I haven't got that far in Cobbler, but "*.*" is a
windows thing and will
*only* match files that have a "." in them. If you do a "ls *.* | wc
-l"
in that directory and then do a "ls * | wc -l" you'll find a very
different number. Any file that doesn't have an extension won't get copied.
If you do a "*" you should get everything.
However I have no idea how to really fix #1. :(
I was working on that first.
> Just to see if it changes something try:
>
> default linux
> prompt 0
> timeout 1
> label linux
> kernel images/ESX-5.0-x86_64/mboot.c32
> ipappend 2
> append -c images/ESX-5.0-x86_64/boot.cfg
>
> **just** that and see if it gets further.
>
> Note also relative paths.
>
> And make sure boot.cfg
>
> On 14/2/25 4:14 PM, Outland, Mike wrote:
>> I’m not using menu, I’m using a file generated by Cobbler which is
>> the MAC of the system which is PXE booting. Here are the contents
>> of that file.
>> [root@cobbler pxelinux.cfg]# cat 01-88-43-e1-c2-b2-ee
>> default linux
>> prompt 0
>> timeout 1
>> label linux
>> kernel /images/ESX-5.0-x86_64/mboot.c32
>> ipappend 2
>> append /images/ESX-5.0-x86_64/vmkboot.gz
>> BOOTIF=01-88-43-e1-c2-b2-ee
>> ks=http://10.21.111.195/cblr/svc/op/ks/system/devops1 lang= text
>> --- /images/ESX-5.0-x86_64/vmkernel.gz ---
>> /images/ESX-5.0-x86_64/sys.vgz --- /images/ESX-5.0-x86_64/cim.vgz
>> --- /images/ESX-5.0-x86_64/ienviron.vgz ---
>> /images/ESX-5.0-x86_64/install.vgz
>>
>>
>> I even tried adding the line:
>> append -c /images/ESX-5.0-x86_64/boot.cfg
>> Which made no difference, still searching for //boot.cfg.
>>
>> This is what I’m seeing while running cobbler sync, towards the end
>> of the run.
>> processing boot_files for distro: ESX-5.0-x86_64
>> failed to copy file
>> /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
>> $img_path/mboot.c32 for ESX-5.0-x86_64
>>
>> On Feb 25, 2014, at 12:22 PM, Petro <petro(a)cpetro.us
>> <mailto:petro@cpetro.us>> wrote:
>>
>>> On 14/2/25 12:27 PM, Outland, Mike wrote:
>>>> Petro,
>>>> Thank you for the quick response.
>>>>
>>>> I’m wondering why this is the case. I am only using the default options
for tftp and cobbler in this regard. Something must be instructing the system to look for
/boot.cfg instead of /images/ESX-5.0-x86_64/.
>>> I can't really answer that, sorry. It's been a *long* time since
>>> I've been that deep in PXE booting/TFTP, and I haven't done cobbler
>>> with TFTP, and I haven't used either for ESX.
>>>
>>> I suspect that something in the ESX process is looking for the
>>> boot.cfg. My best guess is something in menu.
>>>
>>> This might help:
>>>
>>>
http://www.routereflector.com/2014/01/unattended-vmware-esxi-installation...
>>>
>>> Note these bits in particular:
>>> # cat /mnt/boot.cfg | sed -e "s#/##g" -e
"3s#^#prefix=esxi-5.1.0u1-1065491\n#" >
/tftpboot/pxe/esxi-5.1.0u1-1065491/boot.cfg
>>> and
>>>
>>> # vi /tftpboot/pxe/pxelinux.cfg/default
>>> default menu.c32
>>> prompt0
>>> timeout300
>>>
>>> menu title PXEBoot Menu
>>>
>>> labellocal
>>> menu label^0 - Boot from first hard drive
>>> com32 chain.c32
>>> append hd0
>>>
>>> label1
>>> menu label^1 - Install VMware ESXi 5.1.0u1
>>> * kernel esxi**-**5.1**.**0u1**-**1065491**/**mboot**.**c32
>>> append**-**c esxi**-**5.1**.**0u1**-**1065491**/**boot**.**cfg
ks**=**http**:**//172.31.30.1/ks/esxi-5.1.0u1.cfg*
>>>
>>>
>>>> Why would the cobbler templates not generate the boot.cfg in the proper
location if it is infact in the tftpboot directory and not in the distro directory? I
would imagine if you had more than one ESX distro you would then have collisions on the
boot.cfg. I think something else is at play here.
>>>>
>>>> Also how do I get the system to properly copy all the boot files to the
tftp directory when running cobbler sync?
>>>
>>> What happens right now when you run cobbler sync?
>>>
>>> The top few lines of my output are:
>>>
>>> task started: 2014-02-25_132124_sync
>>> task started (id=Sync, time=Tue Feb 25 13:21:24 2014)
>>> running pre-sync triggers
>>> cleaning trees
>>> removing: /var/lib/tftpboot/pxelinux.cfg/default
>>> removing: /var/lib/tftpboot/grub/efidefault
>>> removing: /var/lib/tftpboot/grub/images
>>> removing: /var/lib/tftpboot/s390x/profile_list
>>> copying bootloaders
>>> copying: /usr/share/syslinux/pxelinux.0 -> /var/lib/tftpboot/pxelinux.0
>>> copying: /usr/share/syslinux/menu.c32 -> /var/lib/tftpboot/menu.c32
>>> copying: /usr/share/syslinux/memdisk -> /var/lib/tftpboot/memdisk
>>> copying distros
>>> copying images
>>>
>>>
>>> But this is a non-production "I'm just playing with it"
environment
>>> that I started setting up last week, so I haven't really dug into
>>> it yet, and since my soon to be future employer doesn't use it, it
>>> might get blown away.
>>>
>>> Regards,
>>> Petro.
>>> :wq
>>>
>>> _______________________________________________
>>> cobbler mailing list
>>> cobbler(a)lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org>
>>> https://lists.fedorahosted.org/mailman/listinfo/cobbler
>>
>>
>>
>> _______________________________________________
>> cobbler mailing list
>> cobbler(a)lists.fedorahosted.org
>> https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org>
> https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
7 p.m.
Ok, I was able to work around the problem by making my distro look like this.
Name : ESX-5.0-x86_64
Architecture : x86_64
TFTP Boot Files : {'$local_img_path/net-tg3.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-tg3.v00',
'$local_img_path/scsi-fni.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-fni.v00',
'$local_img_path/net-s2io.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-s2io.v00',
'$local_img_path/net-bnx2.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-bnx2.v01',
'$local_img_path/scsi-adp.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-adp.v00',
'$local_img_path/scsi-bnx.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-bnx.v01',
'$local_img_path/net-be2n.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-be2n.v00',
'$local_img_path/boot.cfg':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/boot.cfg',
'$local_img_path/net-nx-n.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-nx-n.v00',
'$local_img_path/sata-ata.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/sata-ata.v00',
'$local_img_path/ata-pata.v02':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v02',
'$local_img_path/ata-pata.v05':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v05',
'$local_img_path/ata-pata.v04':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v04',
'$local_img_path/ata-pata.v07':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v07',
'$local_img_path/ata-pata.v06':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v06',
'$local_img_path/net-e100.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-e100.v00',
'$local_img_path/net-e100.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-e100.v01',
'$local_img_path/s.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/s.v00',
'$local_img_path/b.b00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/b.b00',
'$local_img_path/efiboot.img':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/efiboot.img',
'$local_img_path/scsi-lpf.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-lpf.v00',
'$local_img_path/sata-sat.v02':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/sata-sat.v02',
'$local_img_path/sata-sat.v03':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/sata-sat.v03',
'$local_img_path/sata-sat.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/sata-sat.v00',
'$local_img_path/sata-sat.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/sata-sat.v01',
'$local_img_path/net-qlcn.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-qlcn.v00',
'$local_img_path/ima-qla4.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ima-qla4.v00',
'$local_img_path/scsi-meg.v02':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-meg.v02',
'$local_img_path/block-cc.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/block-cc.v00',
'$local_img_path/imgdb.tgz':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/imgdb.tgz',
'$local_img_path/net-ixgb.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-ixgb.v00',
'$local_img_path/isolinux.cfg':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/isolinux.cfg',
'$local_img_path/scsi-aic.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-aic.v00',
'$local_img_path/net-sky2.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-sky2.v00',
'$local_img_path/net-r816.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-r816.v01',
'$local_img_path/net-qlge.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-qlge.v00',
'$local_img_path/isolinux.bin':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/isolinux.bin',
'$local_img_path/scsi-hps.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-hps.v00',
'$local_img_path/vmware-esx-base-readme':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/vmware-esx-base-readme',
'$local_img_path/weaselin.i00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/weaselin.i00',
'$local_img_path/misc-cni.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/misc-cni.v00',
'$local_img_path/net-forc.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-forc.v00',
'$local_img_path/scsi-aac.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-aac.v00',
'$local_img_path/boot.cat':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/boot.cat',
'$local_img_path/scsi-ips.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-ips.v00',
'$local_img_path/ehci-ehc.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ehci-ehc.v00',
'$local_img_path/sata-ahc.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/sata-ahc.v00',
'$local_img_path/scsi-bnx.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-bnx.v00',
'$local_img_path/ipmi-ipm.v02':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ipmi-ipm.v02',
'$local_img_path/a.b00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/a.b00',
'$local_img_path/uhci-usb.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/uhci-usb.v00',
'$local_img_path/ipmi-ipm.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ipmi-ipm.v01',
'$local_img_path/scsi-qla.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-qla.v01',
'$local_img_path/scsi-qla.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-qla.v00',
'$local_img_path/net-r816.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-r816.v00',
'$local_img_path/net-bnx2.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-bnx2.v00',
'$local_img_path/scsi-rst.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-rst.v00',
'$local_img_path/net-enic.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-enic.v00',
'$local_img_path/misc-dri.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/misc-dri.v00',
'$local_img_path/ata-pata.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v01',
'$local_img_path/net-cnic.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-cnic.v00',
'$local_img_path/ata-pata.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v00',
'$local_img_path/safeboot.c32':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/safeboot.c32',
'$local_img_path/net-igb.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/net-igb.v00',
'$local_img_path/ipmi-ipm.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ipmi-ipm.v00',
'$local_img_path/useropts.gz':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/useropts.gz',
'$local_img_path/scsi-meg.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-meg.v00',
'$local_img_path/scsi-meg.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-meg.v01',
'$local_img_path/k.b00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/k.b00',
'$local_img_path/vmware-esx-base-osl.txt':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/vmware-esx-base-osl.txt',
'$local_img_path/scsi-mpt.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-mpt.v00',
'$local_img_path/scsi-mpt.v01':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-mpt.v01',
'$local_img_path/scsi-mpt.v02':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/scsi-mpt.v02',
'$local_img_path/ata-pata.v03':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ata-pata.v03',
'$local_img_path/menu.c32':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/menu.c32',
'$local_img_path/ohci-usb.v00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/ohci-usb.v00',
'$local_img_path/tools.t00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/tools.t00',
'$local_img_path/tboot.b00':
'/var/www/cobbler/ks_mirror/ESX-5.0-x86_64/tboot.b00'}
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 : {'/etc/cobbler/pxe/bootcfg_esxi5.template':
'/var/lib/tftpboot/boot.cfg'}
On Feb 26, 2014, at 12:44 PM, Petro <petro@cpetro.us<mailto:petro@cpetro.us>>
wrote:
On 14/2/26 12:25 PM, Outland, Mike wrote:
Petro,
That did not change anything. I still can’t figure out where Cobbler is configure to tell
the system to look for /boot.cfg. If I can get past that, I can complete this task.
There's at 4 different systems or packages interacting here. DHCP, TFTP, PXE. My bet
at this point is that Cobbler isn't doing anything (whether it should or not I'm
not sure. I think most of these files are outside of cobbler control. The Cobbler Devs can
certainly tell me I'm wrong).
This is from your first email (or at least the first email I've seen):
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
What happens here is that the pxeboot stuff on your physical host is making a request for
"pxelinux.0" which loads and runs. Pxelinux.0 then starts making requests for
pxelinux.cfg/40867f18-bb4b-df11-93ef-8843e1c2b2e8 and then
pxelinux.cfg/01-88-43-e1-c2-b2-ee. It finds pxelinux.cfg/01-88-43-e1-c2-b2-ee which is a
configuration file which originally had:
###
default linux
prompt 0
timeout 1
label linux
kernel /images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append /images/ESX-5.0-x86_64/vmkboot.gz BOOTIF=01-88-43-e1-c2-b2-ee
ks=http://10.21.111.195/cblr/svc/op/ks/system/devops1 lang= text ---
/images/ESX-5.0-x86_64/vmkernel.gz --- /images/ESX-5.0-x86_64/sys.vgz ---
/images/ESX-5.0-x86_64/cim.vgz --- /images/ESX-5.0-x86_64/ienviron.vgz ---
/images/ESX-5.0-x86_64/install.vgz
###
When mboot.c32 runs it makes a request for "/boot.cfg". I suspect that something
in pxelinux.cfg/01-88-43-e1-c2-b2-ee isn't quite right and the "-c
images/ESX-5.0-x86_64/boot.cfg" isn't getting passed properly.
We changed the images/ESX-5.0-x86_64/boot.cfg file to look like:
default linux
prompt 0
timeout 1
label linux
kernel images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append -c images/ESX-5.0-x86_64/boot.cfg
right? But it's still looking for /boot.cfg.
What happens if you do:
label linux
kernel images/ESX-5.0-x86_64/mboot.c32
append -c images/ESX-5.0-x86_64/boot.cfg
And if that works, stick the ipappend 2 back in and see if that breaks it again.
What does your DHCP config look like for this group?
On a side note I was able to get this to work by a few manual steps.
1.) Copy the boot.cfg from the /var/lib/tftpboot/images/ESX-5.0-x86_64 directory to the
/var/lib/tftpboot
Yeah, that doesn't surprise me.
2.) Manually copy all files from /var/www/cobbler/ks_mirror/ESX-5.0-x86_64 to
/var/lib/tftpboot/images/ESX-5.0-x86_64
I think I can fix #2 by listing out each file explicitly in the TFTP_boot files for the
distro instead of asking for *.* which causes the copy failure on an existing file (kernel
and initrd specified in the distro).
I haven't got that far in Cobbler, but "*.*" is a windows thing and will
*only* match files that have a "." in them. If you do a "ls *.* | wc
-l" in that directory and then do a "ls * | wc -l" you'll find a very
different number. Any file that doesn't have an extension won't get copied.
If you do a "*" you should get everything.
However I have no idea how to really fix #1. :(
I was working on that first.
Just to see if it changes something try:
default linux
prompt 0
timeout 1
label linux
kernel images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append -c images/ESX-5.0-x86_64/boot.cfg
**just** that and see if it gets further.
Note also relative paths.
And make sure boot.cfg
On 14/2/25 4:14 PM, Outland, Mike wrote:
I’m not using menu, I’m using a file generated by Cobbler which is the MAC of the system
which is PXE booting. Here are the contents of that file.
[root@cobbler pxelinux.cfg]# cat 01-88-43-e1-c2-b2-ee
default linux
prompt 0
timeout 1
label linux
kernel /images/ESX-5.0-x86_64/mboot.c32
ipappend 2
append /images/ESX-5.0-x86_64/vmkboot.gz BOOTIF=01-88-43-e1-c2-b2-ee
ks=http://10.21.111.195/cblr/svc/op/ks/system/devops1 lang= text ---
/images/ESX-5.0-x86_64/vmkernel.gz --- /images/ESX-5.0-x86_64/sys.vgz ---
/images/ESX-5.0-x86_64/cim.vgz --- /images/ESX-5.0-x86_64/ienviron.vgz ---
/images/ESX-5.0-x86_64/install.vgz
I even tried adding the line:
append -c /images/ESX-5.0-x86_64/boot.cfg
Which made no difference, still searching for //boot.cfg.
This is what I’m seeing while running cobbler sync, towards the end of the run.
processing boot_files for distro: ESX-5.0-x86_64
failed to copy file /var/www/cobbler/ks_mirror/ESX-5.0-x86_64/mboot.c32 to
$img_path/mboot.c32 for ESX-5.0-x86_64
On Feb 25, 2014, at 12:22 PM, Petro <petro@cpetro.us<mailto:petro@cpetro.us>>
wrote:
On 14/2/25 12:27 PM, Outland, Mike wrote:
Petro,
Thank you for the quick response.
I’m wondering why this is the case. I am only using the default options for tftp and
cobbler in this regard. Something must be instructing the system to look for /boot.cfg
instead of /images/ESX-5.0-x86_64/.
I can't really answer that, sorry. It's been a *long* time since I've been
that deep in PXE booting/TFTP, and I haven't done cobbler with TFTP, and I haven't
used either for ESX.
I suspect that something in the ESX process is looking for the boot.cfg. My best guess is
something in menu.
This might help:
http://www.routereflector.com/2014/01/unattended-vmware-esxi-installation...
Note these bits in particular:
# cat /mnt/boot.cfg | sed -e "s#/##g" -e
"3s#^#prefix=esxi-5.1.0u1-1065491\n#" >
/tftpboot/pxe/esxi-5.1.0u1-1065491/boot.cfg
and
# vi /tftpboot/pxe/pxelinux.cfg/default
default menu.c32
prompt 0
timeout 300
menu title PXE Boot Menu
label local
menu label ^0 - Boot from first hard drive
com32 chain.c32
append hd0
label 1
menu label ^1 - Install VMware ESXi 5.1.0u1
kernel esxi-5.1.0u1-1065491/mboot.c32
append -c esxi-5.1.0u1-1065491/boot.cfg ks=http://172.31.30.1/ks/esxi-5.1.0u1.cfg
Why would the cobbler templates not generate the boot.cfg in the proper location if it is
infact in the tftpboot directory and not in the distro directory? I would imagine if you
had more than one ESX distro you would then have collisions on the boot.cfg. I think
something else is at play here.
Also how do I get the system to properly copy all the boot files to the tftp directory
when running cobbler sync?
What happens right now when you run cobbler sync?
The top few lines of my output are:
task started: 2014-02-25_132124_sync
task started (id=Sync, time=Tue Feb 25 13:21:24 2014)
running pre-sync triggers
cleaning trees
removing: /var/lib/tftpboot/pxelinux.cfg/default
removing: /var/lib/tftpboot/grub/efidefault
removing: /var/lib/tftpboot/grub/images
removing: /var/lib/tftpboot/s390x/profile_list
copying bootloaders
copying: /usr/share/syslinux/pxelinux.0 -> /var/lib/tftpboot/pxelinux.0
copying: /usr/share/syslinux/menu.c32 -> /var/lib/tftpboot/menu.c32
copying: /usr/share/syslinux/memdisk -> /var/lib/tftpboot/memdisk
copying distros
copying images
But this is a non-production "I'm just playing with it" environment that I
started setting up last week, so I haven't really dug into it yet, and since my soon
to be future employer doesn't use it, it might get blown away.
Regards,
Petro.
:wq
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org<mailto:cobbler@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
3718
days inactive
3725
days old
cobbler@lists.fedorahosted.org
22 comments
4 participants
participants (4)
-
Jörgen Maas -
Outland, Mike -
Petro -
Speagle , Andy