[syslinux] Fwd: syslinux-6.03 failed to boot ESXI 6.7
adancalderon at gmail.com
Wed Mar 13 06:26:44 PDT 2019
---------- Forwarded message ---------
From: Adan Calderon <adancalderon at gmail.com>
Date: Wed, Mar 13, 2019 at 9:13 AM
Subject: Re: [syslinux] syslinux-6.03 failed to boot ESXI 6.7
To: luckydog xf <luckydogxf at gmail.com>
I can share some working examples for a USB Thumb drive and PXE servers
using chain loading, but it will take me some time. If you are interested
in my working configs allow me some time to better document what I have
Going off on a tangent with this, the source code to VMWare's version of
mboot is available when you get the source code from their site. It's a
giant DVD ISO file; in it a file called efiboot-....tgz has it. I did a
google search and found a file here:
It's GPL 2
In case someone want's to look at it.
On Wed, Mar 13, 2019 at 1:36 AM luckydog xf <luckydogxf at gmail.com> wrote:
> Thanks everyone.
> Yes, I used syslinux v4.05, it was sucessful.
> Speaking of chainloading, does it need to build another suite of
> DHCP+TFTP+pxelinux.cfg ? I'm not quite fimilar with it.
> By the way, I also used ipxe, it seem it works with ESXI v6.7.
> Hope it's not *offensive *in this thread, as it's syslinux topics. :)
> --- a sample conf of ipxe for your reference ---
> # make sure you configure boot.cfg correctly.
> # boot.cf
> # kernelopt=http://172.16.234.112/images/esxi67/ks.cfg
> # IPXE
> # UEFI
> kernel http://172.16.234.112/images/esxi67/efi/boot/bootx64.efi -c
> # legacy.
> #kernel http://172.16.234.112/images/esxi67/mboot.c32 -c
> On Wed, Mar 13, 2019 at 3:53 AM Adan Calderon <adancalderon at gmail.com>
>> The mboot.c32 that comes with ESXi is diffrent from the mboot from
>> syslinux. In fact vmware's mboot has it source code available as a
>> It works with versions of Syslinux before 4.05. I have had success using
>> it with more modern versions of syslinux via chainloading. One can chain
>> load an earlier version of syslinux, usually 4.05. This version of
>> syslinux can then run the vmware version of mboot.
>> On Tue, Mar 12, 2019 at 6:06 AM luckydog xf via Syslinux <
>> syslinux at syslinux.org> wrote:
>>> Hello, list,
>>> I'm buiding syslinux6.3 with ESXI6.7, but it says,
>>> * failed to load COM32 File
>>> Here is my config:
>>> label esxi
>>> menu label ESXI-6.7 ^Installer
>>> kernel http://172.16.234.112/images/esxi67/mboot.c32
>>> append -c http://172.16.234.112/images/esxi67/boot.cfg
>>> Seeing from http access log, mboot.c32 was loading successfully.
>>> 172.16.235.99 - - [12/Mar/2019:17:59:15 +0800] "GET
>>> /images/esxi67/mboot.c32 HTTP/1.0" 200 90088 "-" "Syslinux/6.03"
>>> I read from Common problems of docs, and rename mboot.c32 to mboot
>>> accordingly, it raises the same error.
>>> But the way, where is the correct way of booting from local drive?
>>> * localboot 0X80 * or -1 does not work.
>>> Syslinux mailing list
>>> Submissions to Syslinux at syslinux.org
>>> Unsubscribe or set options at:
More information about the Syslinux