Prefix= serverhostname/packetnet-ipxe/esxi/6.7/iso Kernel mboot.c32 -c serverhostname/packetnet-ipxe/esxi/6.7/boot.cfg ip=$ nameserver=8.8.8.8 Here is the latest version of our iPXE script:
We have observed in several examples that some people have referred to the HTTP server hosting the ks.cfg file by it's IP address instead of it's hostname, but our web server requires a hostname to be supplied, and so this is simply not an option for us.
We know the network adapter is working and is able to reach the HTTP server, because in order for the installer to get to the point of displaying this message, many of the installation image files had to be downloaded from the exact same HTTP server that hosts the ks.cfg file. No matter what we do, we receive the following error from the installer (our actual HTTP server hostname is replaced below and throughout this post with serverhostname).Į/esxi/6.7/ks.cfg) connection failed. We have spent hours trying every possible combination of the boot options documented here, and we have tried supplying those boot options as arguments to the iPXE 'kernel' command as well as in the 'kernelopt' boot.cfg option line.
We have sucessfully gotten the VMware ESXi 6.7 installer to boot from a HTTP server using iPXE (and automatically enable the serial console), but we are running into problems getting the fully booted installer to download and use the supplied kickstart config file.