/build/static/layout/Breadcrumb_cap_w.png
11/01/2018 333 views
Hello,

Is anyone able to successfully PXE boot EFI images in vSphere? Our workstations are able to PXE and bring down the image using efi with no problem, but virtual images we are not. We were able to capture images with ease using legacy bios in VMware but not with efi. If anyone has any information on this issue it would be much appreciated. 

Thank you,

VMware 6.5
K2000 6.0.425

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

1

--I can't Edit my original Answer--

So I decided to spin up an Ubuntu 14 VM, and installed that ISC DHCP, got it working for both Legacy and UEFI at the same time. :)
Tested with VMWare devices, BIOS and EFI, all good. KACE SDA version 6.x.

Here is my conf file, I will write up an Article about it:


Answered 11/06/2018 by: Channeler
Red Belt

  • Where 192.168.46.5 is the KACE SDA IP.

    Source Guides used:

    https://en.wikiversity.org/wiki/Configure_ISC-DHCP_server

    and

    https://support.quest.com/kb/218475/linux-dhcp-configuration-via-dhcpd

All Answers

0
It is perfectly possible, first make sure your DHCP for that VM Network is configured to handle UEFI PXE requests:

https://support.quest.com/kace-systems-deployment-appliance/kb/217556/dhcp-configuration-for-bios-and-uefi-pxe


Probably the Scope where those VMs are stored, doesn't have the Options set for UEFI, check your DHCP.

Also make sure the Network Adapter type is E1000,  not E1000E or VMXNET3.
Answered 11/01/2018 by: Channeler
Red Belt

  • Thank you for the response. DHCP is configured correctly and the VMs are in the same scope. Anytime I go to boot to the EFI Network on the VM I receive >>>Start PXE over IPv4. It does not proceed any further.
    • That means the VM is unable to find a DHCP in charge of routing UEFI requests.

      If BIOS works fine, then it is a DHCP\Compatibility issue, again make sure the NIC type is E1000.

      What type of DHCP do you have?
      • NIC is set to E1000

        DHCP type is ISC 4.3.5

        I agree it does seem like a compatibility issue .
      • Linux?, Could you post the current configuration?
      • New PXE boot for KASE
        next-server 172.30.10.50;
        filename "ipxe.efi";
        option tftp-server-name "172.30.10.50";
        option bootfile-name "ipxe.efi";
      • Try to follow this method:
        option k2000-option244 code 244 = ip-address;
        option k2000-option244 172.30.10.50;
        next-server 172.30.10.50;
        filename "ipxe.efi";

        OR

        https://www.itninja.com/blog/view/how-to-configure-dhcp-isc-for-k2000-usage

        Do you know if that ISC can be deployed to Ubuntu Workstations OS, or is that for Ubuntu Servers only?
    • All our workstations are windows and can pxe boot using efi with no problem. Its only when I create images using efi in vsphere that I have the problems.
      • Are those workstations using that same DHCP?
    • I will try that method and let you know the result, thanks.
    • Correct the workstations use the same dhcp.
      • So I decided to spin up an Ubuntu 14 VM, and installed that ISC DHCP, got it working for both Legacy and UEFI at the same time. :)

        Here is my conf file, I will write up an Article about it. (see the main Answer Post)
  • Will the config file work for Windows servers?
    • it should work with anything, iPXE does not care about what OS is being executed.

      It's a deal between the BIOS and the TFTP server.

      I am able to iPXE and load KBEs to machines that don't have a HDD/SSD installed.

      NOTE: if you are talking about using that Config file with a Windows DHCP Server, then no, that is only for Linux. For Windows, read this article:
      https://support.quest.com/kace-systems-deployment-appliance/kb/217556/dhcp-configuration-for-bios-and-uefi-pxe