ipxe (1.21.1+git20220113.fbbdc3926+dfsg-3) unstable; urgency=medium ipxe now splits bootable images and grub scripts into a new binary package: grub-ipxe. This includes ipxe.lkrn for BIOS on i386 / amd64, ipxe.efi for UEFI on all supported architectures, and some relative maintainer scripts to add / remove ipxe to / from the grub menu. If you are booting ipxe physically on your machine, please make sure grub-ipxe is also installed. Should you are using handcrafted grub configs / scripts for ipxe, we suggest removing them and re-generate the grub config to avoid possible duplication / conflicts. -- Shengqi Chen Mon, 03 Feb 2025 04:23:45 +0800 ipxe-qemu (1.21.1+git20220113.fbbdc3926+dfsg-1) unstable; urgency=medium The UEFI network boot ROMs for qemu provided by ipxe-qemu, i.e., efi-$nic.rom have now removed ipxe stack, and can only be used as network drivers for the UEFI firmware to perform network boot (i.e. PXE or HTTP boot). This change is made to avoid size change of ROM files (which breaks qemu live migration). For all users running x86-64 qemu VMs with UEFI firmware and use network boot, please check: 1. If you rely on custom iPXE scripts to boot, you now must first chain-load iPXE by supplying ipxe.efi (which can be obtained from ipxe package) to the clients during the firmware network boot process (typically via a TFTP or HTTP server). Detailed instructions can be found at [1]. 2. If you are just chain-loading EFI images, no further action is required. Users who (0) do not use boot ROMs from ipxe-qemu, or (1) run VMs with legacy BIOS firmware, or (2) run non-x86 VMs, or (3) do not use network boot are not affected by this change and can safely ignore this NEWS. [1]: https://ipxe.org/howto/chainloading -- Miao Wang Mon, 07 Apr 2025 17:12:00 +0800