These iPXE disks will automatically load into boot.netboot.xyz:
| Type | DHCP Bootloaders | Static Bootloaders | Description |
|---|---|---|---|
| ISO | netboot.xyz-dhcp.iso | netboot.xyz-static.iso | Used for CD/DVD, Virtual CDs like DRAC/iLO, VMware, Virtual Box |
| USB | netboot.xyz-dhcp.usb | netboot.xyz-static.usb | Used for creation of USB Keys |
| Kernel | netboot.xyz-dhcp.lkrn | netboot.xyz-static.lkrn | Used for booting from GRUB/EXTLINUX |
| DHCP | netboot.xyz-dhcp.kpxe | netboot.xyz-static.kpxe | DHCP boot image file, uses built-in iPXE NIC drivers |
| DHCP-undionly | netboot.xyz-dhcp-undionly.kpxe | netboot.xyz-static-undionly.kpxe | DHCP boot image file, use if you have NIC issues |
The DHCP bootloaders will automatically get a network address if you have DHCP on your network while the static bootloaders will prompt you for network information.
SHA256 checksums are generated during each build of iPXE and are located here. You can also view the scripts that are embedded into the images here.
netboot.xyz is a convenient place to boot into any type of operating system or utility disk without the need of having to go spend time retrieving the ISO just to run it. iPXE is used to provide a user friendly menu from within the BIOS that lets you easily choose the OS you want along with any specific types of versions or bootable flags.
If you already have iPXE up and running on the network, you can hit netboot.xyz at anytime by typing:
chain --autofree http://boot.netboot.xyz
Full documentation is at ReadTheDocs:
- Arch Linux
- CentOS
- CoreOS
- Debian
- Fedora
- FreeBSD
- Kali
- Mageia
- OpenBSD
- OpenSUSE
- RancherOS
- Scientific
- TinyCoreLinux
- Ubuntu
- AVG Rescue CD
- Clonezilla
- DBAN
- GParted
- HDT
- Memtest
- Partition Wizard
- Pogostick - Offline Windows Password and Registry Editor
- Super Grub2 Disk
Feel free to open up an issue on github or follow us on twitter. We're also on Freenode IRC in #netbootxyz.
Under the Utilities menu on netboot.xyz, there's an option for "Test netboot.xyz branch". If you've forked the code and have developed a new feature branch, you can use this option to chainload into that branch to test and validate the code. All you need to do is specify your github user name and the name of your branch or abbreviated hash of the commit.