Custom PXE Menu Entry

Support
Log in to reply
  • D

    Hello - I wanted to create a pxe booted ISO from the Custom Boot Entry. Was hoping someone could point out the steps. I basically copied the Current Menu Option..
    kernel http://ipofmyopenemserver/fileIwantToBoot

    Getting "error: can't find command kernel.
    Thank You!

    1
  • D

    As a follow up, I noticed the system does create the Database Entry for the Custom Menu Entry, but sometimes does not update the files in the pxelinux.cfg folder. So possibly the system reads one but not the other. It may be my ignorance as to how the custom entry works. Basic goal is to boot an ISO using PXE. Possibly this is a bug who knows.

    1
  • T

    Are you recreating the boot files after you add the custom entry? You would also need to get the correct syntax to boot the iso you want, if it's even possible to boot it with ipxe. If you can't get it to boot you would probably need to visit the ipxe forums. This isn't really designed to boot anything other than Theopenem, but can be done if you get the correct syntax.

    0
  • D

    I did create the Boot Files after...
    Assuming we just wanted to do it with the Boot Files ISO and not PXE...

    I have done the below with another platform Will not mention here to not have others bail from this Great Product.

    So I think I just have a syntax issue with TheOpenEm.
    Assuming I copy the appropriate files to the correct folders..

    kernel http://x.x.x.x/iso/pcunlocker/wimboot
    initrd http://x.x.x.x/iso/pcunlocker/bootmgr.efi
    initrd http://x.x.x.x/iso/pcunlocker/Boot/BCD bcd
    initrd http://x.x.x.x/iso/pcunlocker/Boot/boot.sdi boot.sdi
    initrd http://x.x.x.x/iso/pcunlocker/sources/boot.wim boot.wim
    boot

    NEW Entry with TheOpenEm
    IF I create a folder called "pcunlocker" in this case...

    kernel pcunlocker/wimboot
    initrd pcunlocker/bootmgr.efi
    initrd pcunlocker/Boot/BCD bcd
    initrd pcunlocker/Boot/boot.sdi boot.sdi
    initrd pcunlocker/sources/boot.wim boot.wim
    boot

    Hope that is clear as mud. I appreciate the feedback.

    1
  • T

    Theopenem doesn't expose files directly. It needs to go through an api, meaning you can't just put a file on there and access it through a url.

    An example for wimboot would be
    http://192.168.56.1:8088/clientimaging/IpxeBoot?filename=wimboot&type=bootimage

    This would require the wimboot file to go in the pxeboot images folder.

    A better way would be just to start up another web server that can serve the files directly. You could just use another port if you want to stay on theopenem server. Then theopenem would only handle transferring the initial pxe file over tftp, the rest would be up to you.

    1