Preparing for UEFI booting
BMC Server Automation supports the use of Unified Extensible Firmware Interface (UEFI), as an alternative to the use of BIOS, for booting hardware over the network during provisioning. To enable the use of UEFI, you must perform the following setup tasks:
Task | Details |
---|---|
Configure the Linux DHCP server for EFI booting | To support EFI booting on Linux, edit the DHCP server configuration file, according to the following steps:
|
Ensure that BMC Server Automation supports UEFI booting for the operating system on the target machine. | Of the target platforms supported for provisioning, UEFI is supported on the following operating systems:
|
Ensure that the target machine is set to UEFI booting. | Ensure that any target machine that you want to provision has EFI-based hardware and is set to use UEFI, rather than BIOS, for booting. For example, if the target machine is a virtual machine in a VMware vSphere environment, you must access the virtual machine properties through the vSphere Client and set boot options to use EFI boot firmware, instead of BIOS. |
On Linux, ensure that you use the Skip Linux Pre-Install image option | UEFI booting on Linux does not support the use of a Gentoo image. Therefore, whenever you add or import devices, select Skip Linux Pre-Install as the boot image file. For more information, see Using-the-Skip-Linux-Pre-Install-image-option. As a result of this limitation, auto-discovery of devices is not possible when using UEFI booting on Linux. |
Define a UEFI partition | During the creation of a system package for the server configuration that you want to install, define a UEFI partition in addition to the root partition (Linux) or primary partition (Windows). Use the Disk Partition tab in the system package to define a UEFI partition with the following settings:
For examples of performing these settings, see the relevant steps in Walkthrough-Provisioning-Linux or Walkthrough-Provisioning-Microsoft-Windows-2012-on-a-bare-metal-machine. |