• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

VirtualBox EFI PXE Boot

Scheduled Pinned Locked Moved
Hardware Compatibility
3
9
6.8k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I
    imagingmaster21
    last edited by Sep 22, 2017, 12:38 PM

    I built a test environment for FOG in VirtualBox and have everything working. I am trying to figure out how to get a EFI VM to PXE boot with Virutalbox. This is set on a Internal Network.

    1 Reply Last reply Reply Quote 0
    • X
      x23piracy
      last edited by x23piracy Sep 22, 2017, 7:04 AM Sep 22, 2017, 1:01 PM

      Not possible, Virtual Box cannot boot pxe in efi, you have to enable legacy for image/deploy actions, after that you can enable efi again for the case you are deploying an efi image.

      Bild Text

      Sounds like there is an workaround maybe…:
      https://forums.virtualbox.org/viewtopic.php?f=1&t=65463

      Hello, one partial solution is to initiate ipxe.efi, from the EFI shell (can be done automatically with startup.nsh), the solution is not complete because at this point, ipxe is not capable of chainload another EFI executable, only some image types, like Linux kernels with EFI STUB, can be loaded, therefore cannot load SYSLinux (syslinux.efi), GRUB2 (grubx64.efi) or any other EFI executable, but is enough to boot any recent Linux distribution, WINPE (through wimboot, abother part of the ipxe project) and some other utilities (like memtest86.efi). The capacity to chainload another EFI executable is being developed for ipxe and syslinux. GRUB2 EFI is the only EFI loader with network capacity that I found to be able to chainload another EFI executable, unfortunately cannot initiate network access in most machines when executed locally (it works perfectly when executed from network). Best regards, Diego.

      Regards X23

      ║▌║█║▌│║▌║▌█

      1 Reply Last reply Reply Quote 0
      • I
        imagingmaster21
        last edited by Sep 22, 2017, 1:15 PM

        @x23piracy
        How would I enable legacy for image/deploy actions? I am new to using FOG.

        X 1 Reply Last reply Sep 22, 2017, 1:25 PM Reply Quote 0
        • X
          x23piracy @imagingmaster21
          last edited by Sep 22, 2017, 1:25 PM

          @imagingmaster21 if you have setup your dhcp to enable both (legacy & efi) you just need to disable efi for the vm and then network boot. (Look at the screenshot i posted).

          ║▌║█║▌│║▌║▌█

          I 1 Reply Last reply Sep 22, 2017, 1:27 PM Reply Quote 0
          • I
            imagingmaster21 @x23piracy
            last edited by Sep 22, 2017, 1:27 PM

            @x23piracy

            I am not seeing a screenshot?

            X 1 Reply Last reply Sep 22, 2017, 1:28 PM Reply Quote 0
            • X
              x23piracy @imagingmaster21
              last edited by Sep 22, 2017, 1:28 PM

              @imagingmaster21 https://i.imgur.com/Cn4PMcL.png

              ║▌║█║▌│║▌║▌█

              I 1 Reply Last reply Sep 22, 2017, 1:41 PM Reply Quote 0
              • I
                imagingmaster21 @x23piracy
                last edited by Sep 22, 2017, 1:41 PM

                @x23piracy
                Okay, here is how I have it configured in my DHCP configuration file on my server, I think it is correct, but correct me if I am wrong:
                0_1506087703092_Capture.PNG
                I was looking at a few links on how it should be configured in DHCP for FOG and I referred to this one below:
                https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

                G 1 Reply Last reply Sep 22, 2017, 2:21 PM Reply Quote 0
                • G
                  george1421 Moderator @imagingmaster21
                  last edited by Sep 22, 2017, 2:21 PM

                  @imagingmaster21 Your dhcp.conf file is wrong.

                  similar to the link provided use example 1 as your base configuration: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1

                  You have no subnet configuration, next server and so many other your dhcp server will not be happy with that config file.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  I 1 Reply Last reply Sep 22, 2017, 3:38 PM Reply Quote 0
                  • I
                    imagingmaster21 @george1421
                    last edited by Sep 22, 2017, 3:38 PM

                    @george1421
                    I got it fixed, seems to be working.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    1 / 1
                    • First post
                      9/9
                      Last post

                    212

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project