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.
Yeah, that doesn't surprise me.
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
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.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 was working on that first.
However I have no idea how to really fix #1. :(
_______________________________________________Just to see if it changes something try:
default linuxprompt 0timeout 1label linuxkernel images/ESX-5.0-x86_64/mboot.c32ipappend 2append -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-eedefault linuxprompt 0timeout 1label linuxkernel /images/ESX-5.0-x86_64/mboot.c32ipappend 2append /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.cfgWhich 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_64failed 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> wrote:
_______________________________________________On 14/2/25 12:27 PM, Outland, Mike wrote:
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.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 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-via-pxe-boot-and-kickstart/
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
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler