This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
appnote:uefihttp [2015/10/07 00:23] mcb30 |
appnote:uefihttp [2015/10/07 00:25] mcb30 |
||
---|---|---|---|
Line 20: | Line 20: | ||
} | } | ||
- | (where **my.web.server** is the DNS name (or IP address) of your web server). | + | where **my.web.server** is the DNS name (or IP address) of your web server. |
| | ||
===== Configuring the web server ===== | ===== Configuring the web server ===== | ||
Line 27: | Line 27: | ||
#!ipxe | #!ipxe | ||
- | kernel vmlinuz initrd=initrd.img | + | kernel http://my.web.server/boot/vmlinuz initrd=initrd.img |
- | initrd initrd.img | + | initrd http://my.web.server/boot/initrd.img |
boot | boot | ||
Line 55: | Line 55: | ||
==== Building OVMF ==== | ==== Building OVMF ==== | ||
- | You can build an OVMF image (for virtual machines such as qemu and kvm) which supports UEFI HTTP Boot. You will need to enable the option | + | You can build an OVMF image (for virtual machines such as qemu and kvm) which supports UEFI HTTP Boot. You will need to edit the build description file ''OvmfPkg/OvmfPkgX64.dsc'' to enable the option |
DEFINE HTTP_BOOT_ENABLE = TRUE | DEFINE HTTP_BOOT_ENABLE = TRUE | ||
- | |||
- | in the build description file ''OvmfPkg/OvmfPkgX64.dsc''. | ||
For OVMF (or any other firmware built from upstream EDK2), the UEFI HTTP Boot option will show up as **EFI Network 1** within the boot selection menu. | For OVMF (or any other firmware built from upstream EDK2), the UEFI HTTP Boot option will show up as **EFI Network 1** within the boot selection menu. | ||