I want to use iPXE as a replacement for grub2 on a multiboot system. The goal is to have the BIOS boot in to the ipxe.efi which will read its configuration from a web server. The web server gives it a config file to for instance boot /EFI/redhat/grubx64.efi.

I am stuck at the point where I chainload another efi file. In the iPXE shell I get this:


Apparently it can load the file but booting into it fails. Searching for hints using the error code has not gotten me far.

Is this the correct way to boot an EFI file from disk? Is this supported at all?

Sorry for the huge post but I wanted to try and include as much info as possible.
I've been trying to get this to work for at least a full week now and I'm not having much luck. I have read through the WinPE instructions several times but the ISO I built with Winbuilder from http://theoven.org appears to be slightly different than the ISO used/referenced in the WinPE instructions as that one appears to be Windows 10 PE and I am trying to boot a Windows 7 PE. For example, there is no bootmgr.exe in my ISO.
I am trying to setup a Windows utility CD that can be PXE booted. In that image, are several apps, like Acronis,several antivirus tools that all get incorporated when using Winbuilder. Checkout theoven.org if you want some great tools to build a very useful ISO.

The memdisk method of booting an ISO doesn't work on my WinPE.iso.
The file structure in the ISO looks like below:
The Programs_SE_x64 is where Winbuilder puts utilities that are set in Winbuilder to "run from CD". I don't really care about anything in there as when I built this ISO, I choose for most of the apps I wanted to be "run from RAM" so they are all in the boot.wim file.

³ BOOTMGR
³ bootmgr.efi
³ CdUsb.Y
³ menu.lst
³ out.txt
³ TheOven_Startup_CD.cmd
³ Win7PE.cd
³
Boot
³ ³ bcd
³ ³ boot.sdi
³ ³ bootfix.bin
³ ³ bootsect.exe
³ ³ etfsboot.com
³ ³ GFXBoot.gfx
³ ³ grldr
³ ³ memdisk
³ ³ memtest.efi
³ ³ memtest.exe
³ ³
³ en-US
³ ³ bootmgr.exe.mui
³ ³ bootsect.exe.mui
³ ³
³ fonts
³ ³ chs_boot.ttf
³ ³ cht_boot.ttf
³ ³ jpn_boot.ttf
³ ³ kor_boot.ttf
³ ³ wgl4_boot.ttf
³ ³
³ IMG
efi
³ boot
³ ³ ³ bcd
³ ³ ³ bootx64.efi
³ ³ ³ cdboot.efi
³ ³ ³ efisys.bin
³ ³ ³
³ ³ fonts
³ ³ chs_boot.ttf
³ ³ cht_boot.ttf
³ ³ jpn_boot.ttf
³ ³ kor_boot.ttf
³ ³ wgl4_boot.ttf
³ ³
³ IMG
³ microsoft
³ boot
³ ³ bcd
³ ³ bcd.LOG
³ ³ bcd.LOG1
³ ³ bcd.LOG2
³ ³ cdboot.efi
³ ³ efisys.bin
³ ³
³ fonts
³ chs_boot.ttf
³ cht_boot.ttf
³ jpn_boot.ttf
³ kor_boot.ttf
³ wgl4_boot.ttf
³
Intel
³ Thunderbolt
³ setup.msi
³
Programs_SE_x64
³ assembly
³ ³ ³ Desktop.ini
³ ³ ³ PublisherPolicy.tme
³ ³ ³ pubpol1.dat
³ ³ ³
³ ³ GAC
³ ³ GAC_32
³ ³ ³ mscorlib
³ ³ ³ 2.0.0.0__b77a5c561934e089
³ ³ ³ big5.nlp
³ ³ ³ bopomofo.nlp
³ ³ ³ ksc.nlp
³ ³ ³ mscorlib.dll
³ ³ ³ normidna.nlp
³ ³ ³ normnfc.nlp
³ ³ ³ normnfd.nlp
³ ³ ³ normnfkc.nlp
³ ³ ³ normnfkd.nlp
³ ³ ³ prc.nlp
³ ³ ³ prcp.nlp
³ ³ ³ sortkey.nlp
³ ³ ³ sorttbls.nlp
³ ³ ³ xjis.nlp
³ ³ ³
³ ³ GAC_64
³ ³ ³ mscorlib
³ ³ ³ 2.0.0.0__b77a5c561934e089
³ ³ ³ big5.nlp
³ ³ ³ bopomofo.nlp
³ ³ ³ ksc.nlp
³ ³ ³ mscorlib.dll
³ ³ ³ normidna.nlp
³ ³ ³ normnfc.nlp
³ ³ ³ normnfd.nlp
³ ³ ³ normnfkc.nlp
³ ³ ³ normnfkd.nlp
³ ³ ³ prc.nlp
³ ³ ³ prcp.nlp
³ ³ ³ sortkey.nlp
³ ³ ³ sorttbls.nlp
³ ³ ³ xjis.nlp
³ ³ ³
³ ³ GAC_MSIL
³ ³ ³ Accessibility
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ Accessibility.dll
³ ³ ³ ³
³ ³ ³ System
³ ³ ³ ³ 2.0.0.0__b77a5c561934e089
³ ³ ³ ³ System.dll
³ ³ ³ ³
³ ³ ³ System.Configuration
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ System.configuration.dll
³ ³ ³ ³
³ ³ ³ System.Configuration.Install
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ System.Configuration.Install.dll
³ ³ ³ ³
³ ³ ³ System.Design
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ System.Design.dll
³ ³ ³ ³
³ ³ ³ System.Drawing
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ System.Drawing.dll
³ ³ ³ ³
³ ³ ³ System.Drawing.Design
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ System.Drawing.Design.dll
³ ³ ³ ³
³ ³ ³ System.Runtime.Remoting
³ ³ ³ ³ 2.0.0.0__b77a5c561934e089
³ ³ ³ ³ System.Runtime.Remoting.dll
³ ³ ³ ³
³ ³ ³ System.Runtime.Serialization
³ ³ ³ ³ 3.0.0.0__b77a5c561934e089
³ ³ ³ ³ System.Runtime.Serialization.dll
³ ³ ³ ³
³ ³ ³ System.Runtime.Serialization.Formatters.Soap
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ System.Runtime.Serialization.Formatters.Soap.dll
³ ³ ³ ³
³ ³ ³ System.Security
³ ³ ³ ³ 2.0.0.0__b03f5f7f11d50a3a
³ ³ ³ ³ System.Security.dll
³ ³ ³ ³
³ ³ ³ System.Windows.Forms
³ ³ ³ ³ 2.0.0.0__b77a5c561934e089
³ ³ ³ ³ System.Windows.Forms.dll
³ ³ ³ ³
³ ³ ³ System.Xml
³ ³ ³ 2.0.0.0__b77a5c561934e089
³ ³ ³ System.XML.dll
³ ³ ³
³ ³ temp
³ ³ tmp
³ BGInfo
³ ³ BGInfo.bgi
³ ³ Bginfo.exe
³ ³ Eula.txt
³ ³ RunBGinfo.exe
³ ³
³ iSwitcher
³ ³ iSwitcher.exe
³ ³
³ Microsoft.NET
³ ³ authman
³ ³ Framework
³ ³ ³ ³ NETFXSBS10.exe
³ ³ ³ ³ netfxsbs12.hkf
³ ³ ³ ³ SharedReg12.dll
³ ³ ³ ³
³ ³ ³ v2.0.50727
³ ³ ³ ³ Accessibility.dll
³ ³ ³ ³ alink.dll
³ ³ ³ ³ csc.exe
³ ³ ³ ³ csc.exe.config
³ ³ ³ ³ csc.rsp
³ ³ ³ ³ cscomp.dll
³ ³ ³ ³ cscompmgd.dll
³ ³ ³ ³ Culture.dll
³ ³ ³ ³ cvtres.exe
³ ³ ³ ³ fusion.dll
³ ³ ³ ³ mscordacwks.dll
³ ³ ³ ³ mscordbc.dll
³ ³ ³ ³ mscordbi.dll
³ ³ ³ ³ mscoree.tlb
³ ³ ³ ³ mscorie.dll
³ ³ ³ ³ mscorjit.dll
³ ³ ³ ³ mscorld.dll
³ ³ ³ ³ mscorlib.dll
³ ³ ³ ³ mscorlib.tlb
³ ³ ³ ³ mscorpe.dll
³ ³ ³ ³ mscorrc.dll
³ ³ ³ ³ mscorsec.dll
³ ³ ³ ³ mscorsn.dll
³ ³ ³ ³ mscorsvc.dll
³ ³ ³ ³ mscorsvw.exe
³ ³ ³ ³ mscortim.dll
³ ³ ³ ³ mscorwks.dll
³ ³ ³ ³ shfusion.chm
³ ³ ³ ³ shfusion.dll
³ ³ ³ ³ ShFusRes.dll
³ ³ ³ ³ sysglobl.dll
³ ³ ³ ³ System.configuration.dll
³ ³ ³ ³ System.Configuration.Install.dll
³ ³ ³ ³ System.dll
³ ³ ³ ³ System.Drawing.Design.dll
³ ³ ³ ³ System.Drawing.dll
³ ³ ³ ³ System.Drawing.tlb
³ ³ ³ ³ System.Runtime.Remoting.dll
³ ³ ³ ³ System.Runtime.Serialization.Formatters.Soap.dll
³ ³ ³ ³ System.Security.dll
³ ³ ³ ³ System.tlb
³ ³ ³ ³ System.Windows.Forms.dll
³ ³ ³ ³ System.Windows.Forms.tlb
³ ³ ³ ³ System.XML.dll
³ ³ ³ ³ TLBREF.DLL
³ ³ ³ ³
³ ³ ³ 1031
³ ³ ³ 1033
³ ³ ³ ³ alinkui.dll
³ ³ ³ ³ cscompui.dll
³ ³ ³ ³ CvtResUI.dll
³ ³ ³ ³ vbc7ui.dll
³ ³ ³ ³ Vsavb7rtUI.dll
³ ³ ³ ³
³ ³ ³ CONFIG
³ ³ ³ ³ ³ DefaultWsdlHelpGenerator.aspx
³ ³ ³ ³ ³ machine.config
³ ³ ³ ³ ³ machine.config.comments
³ ³ ³ ³ ³ machine.config.default
³ ³ ³ ³ ³ web.config
³ ³ ³ ³ ³ web.config.comments
³ ³ ³ ³ ³ web.config.default
³ ³ ³ ³ ³ web_hightrust.config
³ ³ ³ ³ ³ web_hightrust.config.default
³ ³ ³ ³ ³ web_lowtrust.config
³ ³ ³ ³ ³ web_lowtrust.config.default
³ ³ ³ ³ ³ web_mediumtrust.config
³ ³ ³ ³ ³ web_mediumtrust.config.default
³ ³ ³ ³ ³ web_minimaltrust.config
³ ³ ³ ³ ³ web_minimaltrust.config.default
³ ³ ³ ³ ³
³ ³ ³ ³ Browsers
³ ³ ³ ³ avantgo.browser
³ ³ ³ ³ cassio.browser
³ ³ ³ ³ Default.browser
³ ³ ³ ³ docomo.browser
³ ³ ³ ³ ericsson.browser
³ ³ ³ ³ EZWap.browser
³ ³ ³ ³ gateway.browser
³ ³ ³ ³ generic.browser
³ ³ ³ ³ goAmerica.browser
³ ³ ³ ³ ie.browser
³ ³ ³ ³ Jataayu.browser
³ ³ ³ ³ jphone.browser
³ ³ ³ ³ legend.browser
³ ³ ³ ³ MME.browser
³ ³ ³ ³ mozilla.browser
³ ³ ³ ³ netscape.browser
³ ³ ³ ³ nokia.browser
³ ³ ³ ³ openwave.browser
³ ³ ³ ³ opera.browser
³ ³ ³ ³ palm.browser
³ ³ ³ ³ panasonic.browser
³ ³ ³ ³ pie.browser
³ ³ ³ ³ webtv.browser
³ ³ ³ ³ winwap.browser
³ ³ ³ ³ xiino.browser
³ ³ ³ ³
³ ³ ³ GAC
³ ³ ³ MUI
³ ³ ³ ³ 0409
³ ³ ³ ³ mscorsecr.dll
³ ³ ³ ³
³ ³ ³ US
³ ³ Framework64
³ ³ ³ SharedReg12.dll
³ ³ ³
³ ³ v2.0.50727
³ ³ ³ Accessibility.dll
³ ³ ³ alink.dll
³ ³ ³ csc.exe
³ ³ ³ csc.exe.config
³ ³ ³ csc.rsp
³ ³ ³ cscomp.dll
³ ³ ³ cscompmgd.dll
³ ³ ³ Culture.dll
³ ³ ³ cvtres.exe
³ ³ ³ fusion.dll
³ ³ ³ mscordacwks.dll
³ ³ ³ mscordbc.dll
³ ³ ³ mscordbi.dll
³ ³ ³ mscoree.tlb
³ ³ ³ mscorie.dll
³ ³ ³ mscorjit.dll
³ ³ ³ mscorld.dll
³ ³ ³ mscorlib.dll
³ ³ ³ mscorlib.tlb
³ ³ ³ mscorpe.dll
³ ³ ³ mscorpjt.dll
³ ³ ³ mscorrc.dll
³ ³ ³ mscorsec.dll
³ ³ ³ mscorsn.dll
³ ³ ³ mscorsvc.dll
³ ³ ³ mscorsvw.exe
³ ³ ³ mscortim.dll
³ ³ ³ mscorwks.dll
³ ³ ³ shfusion.chm
³ ³ ³ shfusion.dll
³ ³ ³ ShFusRes.dll
³ ³ ³ sysglobl.dll
³ ³ ³ System.configuration.dll
³ ³ ³ System.Configuration.Install.dll
³ ³ ³ System.dll
³ ³ ³ System.Drawing.Design.dll
³ ³ ³ System.Drawing.dll
³ ³ ³ System.Drawing.tlb
³ ³ ³ System.Runtime.Remoting.dll
³ ³ ³ System.Runtime.Serialization.Formatters.Soap.dll
³ ³ ³ System.Security.dll
³ ³ ³ System.tlb
³ ³ ³ System.Windows.Forms.dll
³ ³ ³ System.Windows.Forms.tlb
³ ³ ³ System.XML.dll
³ ³ ³ TLBREF.DLL
³ ³ ³
³ ³ 1031
³ ³ 1033
³ ³ ³ alinkui.dll
³ ³ ³ cscompui.dll
³ ³ ³ CvtResUI.dll
³ ³ ³ vbc7ui.dll
³ ³ ³
³ ³ CONFIG
³ ³ ³ ³ DefaultWsdlHelpGenerator.aspx
³ ³ ³ ³ machine.config
³ ³ ³ ³ machine.config.comments
³ ³ ³ ³ machine.config.default
³ ³ ³ ³ web.config
³ ³ ³ ³ web.config.comments
³ ³ ³ ³ web.config.default
³ ³ ³ ³ web_hightrust.config
³ ³ ³ ³ web_hightrust.config.default
³ ³ ³ ³ web_lowtrust.config
³ ³ ³ ³ web_lowtrust.config.default
³ ³ ³ ³ web_mediumtrust.config
³ ³ ³ ³ web_mediumtrust.config.default
³ ³ ³ ³ web_minimaltrust.config
³ ³ ³ ³ web_minimaltrust.config.default
³ ³ ³ ³
³ ³ ³ Browsers
³ ³ ³ avantgo.browser
³ ³ ³ cassio.browser
³ ³ ³ Default.browser
³ ³ ³ docomo.browser
³ ³ ³ ericsson.browser
³ ³ ³ EZWap.browser
³ ³ ³ gateway.browser
³ ³ ³ generic.browser
³ ³ ³ goAmerica.browser
³ ³ ³ ie.browser
³ ³ ³ Jataayu.browser
³ ³ ³ jphone.browser
³ ³ ³ legend.browser
³ ³ ³ MME.browser
³ ³ ³ mozilla.browser
³ ³ ³ netscape.browser
³ ³ ³ nokia.browser
³ ³ ³ openwave.browser
³ ³ ³ opera.browser
³ ³ ³ palm.browser
³ ³ ³ panasonic.browser
³ ³ ³ pie.browser
³ ³ ³ webtv.browser
³ ³ ³ winwap.browser
³ ³ ³ xiino.browser
³ ³ ³
³ ³ GAC
³ ³ MUI
³ ³ ³ 0409
³ ³ ³ mscorsecr.dll
³ ³ ³
³ ³ US
³ Mozilla Firefox
³ ³ ³ Accessible.tlb
³ ³ ³ AccessibleHandler.dll
³ ³ ³ AccessibleMarshal.dll
³ ³ ³ api-ms-win-core-console-l1-1-0.dll
³ ³ ³ api-ms-win-core-datetime-l1-1-0.dll
³ ³ ³ api-ms-win-core-debug-l1-1-0.dll
³ ³ ³ api-ms-win-core-errorhandling-l1-1-0.dll
³ ³ ³ api-ms-win-core-file-l1-1-0.dll
³ ³ ³ api-ms-win-core-file-l1-2-0.dll
³ ³ ³ api-ms-win-core-file-l2-1-0.dll
³ ³ ³ api-ms-win-core-handle-l1-1-0.dll
³ ³ ³ api-ms-win-core-heap-l1-1-0.dll
³ ³ ³ api-ms-win-core-interlocked-l1-1-0.dll
³ ³ ³ api-ms-win-core-libraryloader-l1-1-0.dll
³ ³ ³ api-ms-win-core-localization-l1-2-0.dll
³ ³ ³ api-ms-win-core-memory-l1-1-0.dll
³ ³ ³ api-ms-win-core-namedpipe-l1-1-0.dll
³ ³ ³ api-ms-win-core-processenvironment-l1-1-0.dll
³ ³ ³ api-ms-win-core-processthreads-l1-1-0.dll
³ ³ ³ api-ms-win-core-processthreads-l1-1-1.dll
³ ³ ³ api-ms-win-core-profile-l1-1-0.dll
³ ³ ³ api-ms-win-core-rtlsupport-l1-1-0.dll
³ ³ ³ api-ms-win-core-string-l1-1-0.dll
³ ³ ³ api-ms-win-core-synch-l1-1-0.dll
³ ³ ³ api-ms-win-core-synch-l1-2-0.dll
³ ³ ³ api-ms-win-core-sysinfo-l1-1-0.dll
³ ³ ³ api-ms-win-core-timezone-l1-1-0.dll
³ ³ ³ api-ms-win-core-util-l1-1-0.dll
³ ³ ³ api-ms-win-crt-conio-l1-1-0.dll
³ ³ ³ api-ms-win-crt-convert-l1-1-0.dll
³ ³ ³ api-ms-win-crt-environment-l1-1-0.dll
³ ³ ³ api-ms-win-crt-filesystem-l1-1-0.dll
³ ³ ³ api-ms-win-crt-heap-l1-1-0.dll
³ ³ ³ api-ms-win-crt-locale-l1-1-0.dll
³ ³ ³ api-ms-win-crt-math-l1-1-0.dll
³ ³ ³ api-ms-win-crt-multibyte-l1-1-0.dll
³ ³ ³ api-ms-win-crt-private-l1-1-0.dll
³ ³ ³ api-ms-win-crt-process-l1-1-0.dll
³ ³ ³ api-ms-win-crt-runtime-l1-1-0.dll
³ ³ ³ api-ms-win-crt-stdio-l1-1-0.dll
³ ³ ³ api-ms-win-crt-string-l1-1-0.dll
³ ³ ³ api-ms-win-crt-time-l1-1-0.dll
³ ³ ³ api-ms-win-crt-utility-l1-1-0.dll
³ ³ ³ application.ini
³ ³ ³ breakpadinjector.dll
³ ³ ³ chrome.manifest
³ ³ ³ crashreporter.exe
³ ³ ³ crashreporter.ini
³ ³ ³ d3dcompiler_47.dll
³ ³ ³ dependentlibs.list
³ ³ ³ firefox.exe
³ ³ ³ firefox.VisualElementsManifest.xml
³ ³ ³ freebl3.chk
³ ³ ³ freebl3.dll
³ ³ ³ IA2Marshal.dll
³ ³ ³ lgpllibs.dll
³ ³ ³ libEGL.dll
³ ³ ³ libGLESv2.dll
³ ³ ³ maintenanceservice.exe
³ ³ ³ maintenanceservice_installer.exe
³ ³ ³ minidump-analyzer.exe
³ ³ ³ mozavcodec.dll
³ ³ ³ mozavutil.dll
³ ³ ³ mozglue.dll
³ ³ ³ Mozilla.cfg
³ ³ ³ msvcp140.dll
³ ³ ³ nss3.dll
³ ³ ³ nssckbi.dll
³ ³ ³ nssdbm3.chk
³ ³ ³ nssdbm3.dll
³ ³ ³ omni.ja
³ ³ ³ pingsender.exe
³ ³ ³ platform.ini
³ ³ ³ plugin-container.exe
³ ³ ³ plugin-hang-ui.exe
³ ³ ³ qipcap.dll
³ ³ ³ softokn3.chk
³ ³ ³ softokn3.dll
³ ³ ³ ucrtbase.dll
³ ³ ³ update-settings.ini
³ ³ ³ updater.exe
³ ³ ³ updater.ini
³ ³ ³ vcruntime140.dll
³ ³ ³ xul.dll
³ ³ ³
³ ³ browser
³ ³ ³ ³ blocklist.xml
³ ³ ³ ³ chrome.manifest
³ ³ ³ ³ crashreporter-override.ini
³ ³ ³ ³ omni.ja
³ ³ ³ ³
³ ³ ³ defaults
³ ³ ³ ³ preferences
³ ³ ³ ³ activate.js
³ ³ ³ ³
³ ³ ³ extensions
³ ³ ³ ³ {972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
³ ³ ³ ³
³ ³ ³ features
³ ³ ³ ³ aushelper@mozilla.org.xpi
³ ³ ³ ³ clicktoplay-rollout@mozilla.org.xpi
³ ³ ³ ³ e10srollout@mozilla.org.xpi
³ ³ ³ ³ firefox@getpocket.com.xpi
³ ³ ³ ³ followonsearch@mozilla.com.xpi
³ ³ ³ ³ screenshots@mozilla.org.xpi
³ ³ ³ ³ shield-recipe-client@mozilla.org.xpi
³ ³ ³ ³ webcompat@mozilla.org.xpi
³ ³ ³ ³
³ ³ ³ VisualElements
³ ³ ³ VisualElements_150.png
³ ³ ³ VisualElements_70.png
³ ³ ³
³ ³ defaults
³ ³ ³ pref
³ ³ ³ channel-prefs.js
³ ³ ³
³ ³ dictionaries
³ ³ ³ en-US.aff
³ ³ ³ en-US.dic
³ ³ ³
³ ³ distribution
³ ³ ³ extensions
³ ³ ³ uBlock0@raymondhill.net.xpi
³ ³ ³
³ ³ fonts
³ ³ ³ EmojiOneMozilla.ttf
³ ³ ³
³ ³ gmp-clearkey
³ ³ 0.1
³ ³ clearkey.dll
³ ³ manifest.json
³ ³
³ MultiRes
³ ³ MultiRes.exe
³ ³ MultiRes.exe.manifest
³ ³ MultiRes.htm
³ ³ MultiRes.ini
³ ³
³ Sophos
³ ³ SophosGui.exe
³ ³ unzip.exe
³ ³ WGet.exe
³ ³
³ xCHM
³ xchm-1.23win32.exe
³
sources
boot.wim
The boot.wim that lives in sources and is fairly large (991,263,822 bytes) because when building with winbuilder, you can choose to have your programs run from RAM which puts them all in the boot.wim. The boot.wim also has several drivers installed so it should theoretically work on several different makes and models of laptops and desktops.
I have tried all kinds of combinations (so many I can't remember them all frankly) but I'm hoping that from looking at the file structure above, someone can provide some insight or some example menu entries.

I have a FOG server setup and working correctly. Because I am using it at home, my FIOS router also provides a DHCP server so I want to use DNSMASQ as a DHCP proxy server to handle requests and respond with a TFTP address. So far, this is all working correctly. When I PXE boot, it correctly gets a DHCP address from the FIOS router and DNSMASQ correctly provides the TFTP ip address. IPXE correctly loads but always prompts for a TFTP ip address. I know this usually occurs when there are multiple DHCP servers in the network but I have verified the only DHCP server is the one provided by the FIOS router. DHCPD is stopped on the FOG server. To test this, I disabled the DHCP server on the FIOS router, and the PXE boot just hangs as it never receives an IP address.
I also created a menu entry in the FOG server that executes the "config" command so I could look at the IPXE settings, and I verified that the NEXT-SERVER/Option 66 was correctly set to the ip address of the TFTP server.
If I manually enter the TFTP address, which the same as the FOG server, it PXE boots correctly to the menus entries I have configured on the FOG server.
What I can't figure out is why does IPXE always prompt for a TFTP address when it looks like everything is configured correctly and I have verified there is only the FIOS DHCP router providing DHCP. I'm so close to getting this to work! Help!

Below is my /etc/dnsmasq.d/ltsp.conf file.

port=0

log-dhcp

tftp-root=/tftpboot

dhcp-boot=undionly.kpxe,192.168.1.5

dhcp-option=17,/var/www/html
# tried both of below with no luck but these shouldn't matter since IPXE is loading
# dhcp-option=pxe,66,192.168.1.5
# dhcp-option=66,192.168.1.5

dhcp-option=vendor:PXEClient,6,2b

dhcp-no-override

pxe-prompt=.Press F8 for boot menu., 3

pxe-service=X86PC, .Boot from network., undionly.kpxe

# pxe-service=X86PC, .Boot from local hard disk., 0

dhcp-range=192.168.1.5,proxy,255.255.255.0

I am trying to boot the installation ArchLinux files on my machine with UEFI firmware. I had turned off secure boot.

I am able to reach the iPXE shell from DHCP undionly.ipxe.

Here is my iPXE script that trying to fetch kernel and initrd files from http:


I encounter this error after fetching the files from http service and boot:


This is the ArchLinux ISO files structure:


Thank you.

I am trying to boot ipxe from a usb drive and have it detect my USB to Ethernet adapter, so that I can load my ipxe menu from my web server.

I have built ipxe.efi from the source git ipxe repo. And I am using the Startech 31000s USB Ethernet Adapter which uses the ax88179 chipset. I have loaded ipxe.efi onto a USB drive and tried booting from the usb. The computer successfully loads ipxe from the usb but isn't able to find my USB Ethernet Adapter, it gives the message "no more network devices". How can I make ipxe work with my usb NIC?

I am using an image in the console with my menu, and I have set the console resolution x and y to 1024 x 768. But I find that on some computers the image is stretched. Is there a way that iPXE can dynamically set the resolution to prevent the image from being stretched on displays with different aspect ratios and resolutions?

Im trying to double chain ipxe as following: (i've compiled ipxe.efi with DOWNLOAD_PROTO_HTTPS enable)

First Chain:
#!ipxe
echo info chain http://IPaddr:PORT/ipxe/${net0/mac:hex}
chain http://IPaddr:PORT/ipxe/${net0/mac:hex}

Second Chain:
#!ipxe
echo +--------- ipxe ---------------------------------------------
echo | OS Install
echo | mac.................: ${mac}
echo | uuid................: ${uuid}
echo | serial..............: ${serial}
echo | ip..................: ${ip}
echo | manufacturer........: ${manufacturer}
echo | product.............: ${product}
echo +------------------------------------------------------------
imgfree
set next-server IPaddr2
set filename https://${next-server}:PORT/somedir/tramp
chain https://${next-server}:PORT/somedir/tramp

Inside this file: https://${next-server}:PORT/somedir/tramp
#!gpxe

set max-retries 6
set retry-delay 20
post /some-dir/host-register?bootmac=${mac}

Can I do that ?
If not is there an alternative way to do this ?

ERROR from ipxe:
https://IPaddr2:PORT/some-dir/tramp... Error 0x3e11618e (http://ipxe.org/3e11618e)
Could not boot: Error 0x3e11618e (http://ipxe.org/3e11618e)

hi there.
I have been reading many topics and forums and I am stuck .
I am trying to ipxe boot an iso file. But I need the iso file to load as a cd drive on the machine .
I have a fog project machine setup and I tried the following setup
sanboot --no-describe --drive 0x80 http://xxx.iso
-----------------------------------
initrd http://192.168.7.21/fog/isoimg/trx.iso
chain memdisk ||

even

initrd http://192.168.7.21/fog/isoimg/trx.iso
chain memdisk iso raw ||

it boots ok but the iso check for files on a cd drive during the boot up and it can’t find any so it hangs. I have a usb boot key tool that I use to load different iso
Windows-linux,nas4free, etc
I would like to move that to a pxe platform .
I would like to avoid decompressing iso files. When new builds come out I would like to only replace the iso file.

Any suggestions ?

Hello,

We’ve just recently installed a FOG server. It seems to be working so far as we’ve tested, but after chainloading into iPXE it seems to hang at the “configuring net0(MAC address)” step. I feel like it shouldn’t be hanging for 4-5 minutes at this step before continuing on to the menu. I’ve tried different kernals, different hosts, different .pxe, .kpxe, and kkpxe. What am I missing? What is happening at this stage exactly? Driver for the NIC loading? I can't find anything really describing this issue.

I've opened up a thread on the FOG forums as well:
https://forums.fogproject.org/topic/1137...et0-slowly

Hello gays!
I installed ipxe.lkrn in the first partition of hd, and using syslinux boot. but every time after the reboot the previous settings is missing, I hope settins can be stored permanently, how should I do?

Hello all, I have been working on testing FOG+iPXE configurations with new Aquantia AQN-107 10G NIC's as well as new ASUS XG-C100C 10G NIC's. I have successfully used FOG with the integrated NICs on my machines, however both 10G cards only get as far as chainloading iPXE before getting stuck at configuring the interface with an address. I have done numerous tests and see that the cards are sending out a DHCP request and my server is sending an Offer back, however the NICs do not seem to be picking up incoming traffic. I feel this may be a driver issue with the new cards, so I was wondering if anybody had anything in the works as far as integrating drivers for these new cards. Thanks.

Good day.
I set iPXE on nix(debian+tftp+apache), set options in isc-dhcp
And its works!
But if i start WDS server in same subnet (192.168.0.2 for example) - and NO options for in it DHCP config at all - all pxe clints starts boot from WDS.
what's wrong with is?[/quote]

Hello,
I have an EFI dual-boot setup. (One disk with GPT partitions, including an EFI partition) I'd like to be able to boot locally, and to choose which .efi file to boot. As such, simply using 'exit' will not serve my purposes.
I have iPXE on a USB flash drive. (I've tried both 64-bit EFI and BIOS as well as the default 32-Bit BIOS.)

I expect the command:
to work. However, this simply states that the sanboot device cannot be found in EFI mode (2c222087) or that there is an Input/Output error in BIOS mode.

I've found very little documentation on this issue, with most people opting for the 'exit' method. I found somewhere that it could relate to EFI systems not working with sanboot, but then I see in the documentation that the '--filename' argument is specifically for EFI systems. So this leaves me a bit confused.

If anyone has any advice or suggestions, I'd be very open to hearing them.
Thanks!

Hello,
I have a network adapter "EXPI9301CTBLK", which I wanted to flash now.
I have entered the following commands "BootUtil -SAVEIMAGE -FILE = Backup.FLB" and "BootUtil -FE -ALL". Then I wanted to flash the new firmware with "BootUtil -UP = EFI -ALL-FILE = BOOTIMG.FLB".
Unfortunately, something went wrong.
First came a message that the Nic can not be initialized.
And now the adapter is no longer recognized, so I can not flash back.
Is the adapter still somehow save?

Please excuse my bad English, I write with translator.

Thanks in advance.

Hello, sorry my bad english, i is newer in this fórum, i need help for solve an problem with iPXE rom, before i used gPXE rom, my computers with gigabit pci 32 card boots quickly, approx 15 seconds (normal boot), after use iPXE rom, my PCs boots on 1 minute or freeze on screen boot from drive 0x80 and my hard drive server not sync.

i have tested with pci-e cards with ipxe, my PC boots same my 32 gigabit pci cards using gPXE Rom, i have tested any cards diferente models pci 32, but no sucess with iPXE ROM.

Sorry if i have posted this topic in wrong place.

my script configurations used on gPXE and iPXE rom is same

Follow my script configuration

#!ipxe

ifopen net0
set net0/ip 10.0.0.50
set net0/netmask 255.255.255.0
set net0/gateway 0.0.0.0
set keep-san 1
sanboot iscsi:10.0.0.254:::7:iqn.device:strg-device.01

OBS. this configuration above is same on gPXE and iPXE
my board on i need configure boot lan, has no PCI-e slot

I can record the videos and post here in the forum for better understanding.

Hello.
For example, now I can load only one bootloader/file over cpio over initrd like this(GRUB2):

I want to load multiple files (like in wimboot) over newc and select chain/kernel file to load, like this:

It can be realized?

Hello!
I am puzzled why this does not work (version 1.0.0+ (c9f6 as well as 546dd)):

#!ipxe
echo test
set vartest 200
echo $vartest
echo ${vartest}
sleep 5
exit

It displays
test


only. I was expecting to see
test
200
200

What am I doing wrong?

What I am really trying to do is set up a boot menu but with
choose --timeout 5000 --default ubuntu target
${target} is empty as well

ipxe currently has no native support to boot the FreeBSD kernel, the only way to get to FreeBSD is by chaining to ISO or PXE+NFS.

there are claims to be found on the internet that ipxe can boot 32 bit FreeBSD as a multiboot image. this is not working for x86.

looking at all options, I found out that ipxe in EFI mode (both x86 as well as amd64) can boot the FreeBSD efi loader (loader.efi), but it cannot be configured to add modules like kernel or rootfs, due to limitations of the loader or other incompatibility.

FreeBSD can be directly booted by non-native loaders, e.g. grub2 has support for this (kernel and modules).

Being a rather widely used system I wonder why ipxe has no native support for FreeBSD.

The kernel is an ELF image, but it seems to require relocation after load. I have not found ELF relocation logic in IPXE. Otherwise the loading logic looks very straightforward (setting up an environment and kicking it off).

I wonder how big an effort it would be to add FreeBSD kernel support and if a team could form to perform this change, provided the idea is backed by the core members of ipxe.

Any feedback welcome.

Dear Sir/Madam,

I have installed Ubuntu 16.04 Linux on HP Desktop Computer... Now I want to make a iSCSI Target Server On this Ubuntu Machine With PXE Configuration, DHCP Configuration AND TFTP Configuration Extra Extra ...

Because, Sitting on Other Client Machine, I want to install Windows 7 ON iSCSI Target Server Through iPXE NetBooting...

Please Kindly do the Help in this regard as early as possible

Thanking you and all

Basavaraj From India

OCSP is causing some issues with our network and we'd like to disable it entirely from our binary. Is there an easy method to go about this when building the image from source, or do I have to go in an manually go in an disable certain calls?