Hi Gene, For reference, I'm running into the issue when I PXE boot any ESXi 4.x image. My NICs use the Intel PXE to chainload gpxelinux.0, which then loads the ESXi image like so:
kernel -n esxi http://${next-server}/pxe/mboot.c32 imgargs esxi http://${next-server}/pxe/vmware/esxi-41-latest/vmkboot.gz --- http://${next-server}/pxe/vmware/esxi-41-latest/vmkernel.gz --- http://${next-server}/pxe/vmware/esxi-41-latest/s.z --- http://${next-server}/pxe/vmware/esxi-41-latest/c.z boot esxi The mboot.c32 referenced above is from the syslinux 3.72 provided in RedHat 5. For whatever reason, ESXi wants 2.12 or newer. Ideally, setting it to the actual version would probably be best, but so long as it's set to *something* that works, I'm OK with it ;-) -- Geoffrey Silver Global Infrastructure CITADEL -----Original Message----- From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] On Behalf Of Gene Cumm Sent: Friday, October 22, 2010 3:28 PM To: je...@redhat.com Cc: gpxe@etherboot.org; Casey Dahlin; gco...@redhat.com Subject: Re: [gPXE] [PATCH] Make gpxe report syslinux version 2.12 On Fri, Oct 22, 2010 at 13:05, Jeremy Eder <je...@redhat.com> wrote: > Hi Gene, > > On Fri, 2010-10-22 at 13:00 -0400, Casey Dahlin wrote: >> On Tue, Oct 12, 2010 at 07:37:09PM -0400, Gene Cumm wrote: >> > On Tue, Oct 12, 2010 at 16:29, Casey Dahlin <cdah...@redhat.com> wrote: >> > > Some versions of mboot.c32 shipped by VMWare fail because of a >> > > version check (done with INT 22h with AX set to 0001h). gPXE >> > > appears to use an empty version number (0.0). This patch makes it >> > > return 2.12 >> > >> > Which VMware product(s)/version(s) (ESXi, perhaps?) with what >> > version of mboot.c32? > > VMware ESXi 4.0.1...not sure what version of mboot.c32 actually. Probably the same as the VMware build of mboot.c32 from the ESXi Installable CD, I'd guess. >> Yes, ESXi, I'll have to relay the version question (John, if you're >> reading, feel free to chime in). >> >> > Have you considered using gpxelinux.0 (at gpxe/gpxelinux.0) and any >> > needed modules (like com32/modules/mboot.c32) from the current >> > Syslinux package? gpxelinux.0 in Syslinux 4.02 is at gPXE 1.0.0. > > Hmm, does that version include a fix for this ? Not sure what this > suggestion is meant to test. Yes and no. If you use gpxelinux.0, mboot.c32 will be talking with PXELINUX and not the emulated API in gPXE. However, if you are not using gPXE on top of the hardware's PXE client and using it instead of any hardware-derived client, this would need a little more work (roughly gPXE to load gpxelinux.0 to run mboot.c32). > Either way, the installer is looking for any version. It doesn't have > to be 2.12. Can that field be populated automatically by a macro ? > >> > Why version 2.12? Is that the exact minimum version your mboot.c32 wants? > > Yes, correct...exact minimum...as I mentioned, anything higher would > work just fine as well I would think that it should match the API implemented in gPXE or be zero. I'm not sure if HPA is on this list or not and what his opinion/preference is. As of Syslinux-4.00, there was a big change in the API and COM32 format. -- -Gene _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe CONFIDENTIALITY AND SECURITY NOTICE The contents of this message and any attachments may be confidential and proprietary and also may be covered by the Electronic Communications Privacy Act. This message is not intended to be used by, and should not be relied upon in any way, by any third party. If you are not an intended recipient, please inform the sender of the transmission error and delete this message immediately without reading, disseminating, distributing or copying the contents. Citadel makes no assurances that this e-mail and any attachments are free of viruses and other harmful code. _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
