netboot/pixiecore/README.testing
David Anderson 029be8d339 Force machines to chainload through Pixiecore's embedded iPXE.
This guarantees that we load the real OS from an iPXE with a known
featureset, rather than rely on the firmware iPXEs to be correct.

Also switch to ipxe.pxe for BIOS boots instead of undionly.kpxe.

ipxe.pxe works when you chainload from one iPXE to another, whereas
undionly.kpxe encounters some kind of poorly explained bug where
it loses the ability to configure networking.

Tested against the following configurations:
 - VirtualBox + BIOS w/ iPXE
 - VirtualBox + BIOS w/ Intel UNDI
 - VirtualBox + EFI
 - KVM + SeaBIOS w/ iPXE
 - KVM + OVMF (EFI)
 - Dell R610 + Dell BIOS/PXE

Fixes #51, fixes #52.
2018-01-15 19:17:56 -08:00

14 lines
886 B
Plaintext

# Testing pixiecore
This is a braindump of the different hardware configurations that
exhibit different behaviors.
| Machine | Firmware | PXE firmware | Notes |
| --- | --- | --- | --- |
| Proxmox VM | SeaBIOS | iPXE | |
| Proxmox VM | OVMF | OVMF | Good UEFI baseline, many UEFI firmwares are derived from OVMF/TianoCore/EDK2e |
| VirtualBox (OSS) | VirtualBox BIOS | customized iPXE | Cannot boot with `next-server` and `filename`, must be booted with iPXE-specific commands |
| VirtualBox (w/ extension pack) | VirtualBox BIOS | Intel UNDI | Good BIOS baseline, Intel UNDI is the basis for many BIOS PXE firmwares |
| VirtualBox (OSS) | VirtualBox EFI | ?? | Unclear what the EFI firmware is, but provides more diversity |
| Dell R610 | Dell BIOS | Dell | The only bare metal machine I have right now with remote management. Strange custom firmwares, also a decent variety test. |