The versatile networkboot loader iPXE
Wakeup Call

© Lead Image © nyul, 123RF.com
iPXE simplifies the task of booting images over a network and also lets admins design dynamic boot menus that integrate scripts and boot images via HTTP(S).
Whether you are managing Linux or Windows, most automated provisioning systems depend on booting over the network with the Preboot Execution Environment (PXE). PXE provides the software for a standardized environment before the system actually starts. Within this preboot environment, the admin can influence the startup behavior to respond to special requirements, launch an OS installation process, or take other preliminary steps.
In the Linux world, PXELinux by the SysLinux project [1] is the de facto standard tool for network booting. In the shadow cast by PXELinux, other PXE bootloaders have emerged that make it easier to solve many tasks.
The iPXE project [2] provides a full open source PXE implementation. iPXE calls itself "…the leading open source network boot firmware." The project started life as a fork of gPXE and is still under active development. iPXE also inherits some features from the Etherboot project [3].
The goals for iPXE are to provide the best PXE implementation, make NICS bootable, and support and automate complex scenarios that involve booting from the network.
iPXE directly integrates a full feature set (Figure 1) – without the need for loadable modules. Usage scenarios for an admin implementing iPXE include:

- Displaying dynamic boot menus that differ depending on the boot system or user login
- Booting images via HTTP or HTTPS, also across the Internet
- Launching boot operations via I-SCSI, Fibre Channel over Ethernet (FCoE), or ATA over Ethernet (AoE).
iPXE also boots clients via Tagged VLAN, WiFi, or InfiniBand.
Use the Source!
You can install iPXE through the Debian and Ubuntu package management systems, but the package versions are missing documentation and are not up to date. I recommend building iPXE yourself. (You could also download and burn the ISO image file at the iPXE project website.)
The iPXE build dependencies, gcc
, binutils
, make
, perl
, and syslinux
are quickly installed. It is also a good idea to check out the Git sources so you will benefit from future updates.
The development model for iPXE relies on a stable trunk, whose builds always support use in production environments [4]. iPXE does not have an official release; admins build it in the traditional way, using a Makefile:
git clone git://git.ipxe.org/ipxe.git cd ipxe/src make
The result ends up in the bin/
subdirectory; depending on your requirements, different files are used to start iPXE (Table 1).
Table 1
iPXE Image Types
File Name | Function |
---|---|
|
iPXE boot image |
|
Floppy disk image |
|
Image for USB sticks |
|
CD image for CDs or DVDs |
|
A kernel image used by other bootloaders or Qemu |
|
Image for PXE chain loading |
For RPM systems, I extended iPXE to include a SPEC
file [5], which creates a ready-to-use RPM when you call make rpm
.
Configuration
iPXE is configured using C header files in the config/local
directory. Inspiration for possible configurations is provided by the .h
files in the parent config
directory – each file is responsible for one aspect of iPXE. To edit the entries in console.h
, for example, you need to specify a config/local/console.h
file with the contents of Listing 1.
Listing 1
config/local/console.h
Listing 1 sets a US keyboard layout and enables log output via syslog. With a few additional entries (Listing 2) in config/local/general.h
, you can configure HTTPS support as well as a customized product name, which iPXE displays when booting.
Listing 2
config/local/general.h
When you build the iPXE image, you can embed a script, which the PXE bootloader automatically runs. Each iPXE script starts with #!ipxe
and contains some iPXE commands. A simple script to get you started with dynamic boot environments follows:
#!ipxe dhcp chain http://example.com/boot/script.php
You need to save the file – for example, as script.ipxe
, and integrate it into the build process as follows:
make EMBED=script.ipxe
The iPXE project describes other ways to integrate scripts into the boot process [6].
iPXE generally supports two targets for the boot process: You can boot from a block device or directly download a kernel and an initrd and launch them. You will find precompiled images for the examples described in this article at GitHub [7].
Party SAN
iPXE is the tool of choice for booting a system from an Ethernet storage area network (SAN) [8]; it also supports I-SCSI, FCoE, and AoE. The sanboot
command is for all boot operations that need a block device. sanboot
goes with the URI of the block device; for example, for the I-SCSI LUN:
sanboot iscsi:boot.ipxe.org::::iqn.2010-04. org.ipxe.boot:public
If necessary, sanboot
also boots from the local hard disk:
sanboot --no-describe --drive 0x80
Because sanboot
works at the BIOS level, the block device must possess a normal bootloader, which in turn loads the kernel and initrd
and specifies a matching root device.
A simple option for trying out this process is booting the live FreeDOS CD off the Internet in a Qemu virtual machine (Figure 2); ipxe.lkrn
must reside in the directory from which you invoke the command:

qemu -kernel ipxe.lkrn -append 'dhcp && \ sanboot http://ftp.gwdg.de/pub/misc/freedos/files/\ distributions/1.0/fdfullcd.iso || shell'
Qemu can start iPXE directly in lkrn
format; it passes the iPXE commands as options. If successful, iPXE does not return a message, because it hands over boot control. If iPXE cannot access the URL, the system starts an interactive shell (Figure 3).

Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Direct Download
Read full article as PDF:
Price $2.95
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Find SysAdmin Jobs
News
-
KDE Plasma 5.27 Beta is Ready for Testing
The latest beta iteration of the KDE Plasma desktop is now available and includes some important additions and fixes.
-
Netrunner OS 23 Is Now Available
The latest version of this Linux distribution is now based on Debian Bullseye and is ready for installation and finally hits the KDE 5.20 branch of the desktop.
-
New Linux Distribution Built for Gamers
With a Gnome desktop that offers different layouts and a custom kernel, PikaOS is a great option for gamers of all types.
-
System76 Beefs Up Popular Pangolin Laptop
The darling of open-source-powered laptops and desktops will soon drop a new AMD Ryzen 7-powered version of their popular Pangolin laptop.
-
Nobara Project Is a Modified Version of Fedora with User-Friendly Fixes
If you're looking for a version of Fedora that includes third-party and proprietary packages, look no further than the Nobara Project.
-
Gnome 44 Now Has a Release Date
Gnome 44 will be officially released on March 22, 2023.
-
Nitrux 2.6 Available with Kernel 6.1 and a Major Change
The developers of Nitrux have officially released version 2.6 of their Linux distribution with plenty of new features to excite users.
-
Vanilla OS Initial Release Is Now Available
A stock GNOME experience with on-demand immutability finally sees its first production release.
-
Critical Linux Vulnerability Found to Impact SMB Servers
A Linux vulnerability with a CVSS score of 10 has been found to affect SMB servers and can lead to remote code execution.
-
Linux Mint 21.1 Now Available with Plenty of Look and Feel Changes
Vera has arrived and although it is still using kernel 5.15, there are plenty of improvements sure to please everyone.