Differences

This shows you the differences between two versions of the page.

--- appnote:uefihttp [2015/10/07 00:22]
mcb30
+++ appnote:uefihttp [2015/10/07 00:24]
mcb30
@@ Line 24: / Line 24: @@
 ===== Configuring the web server =====
-Place your iPXE binary (e.g. [[http://boot.ipxe.org/ipxe.efi|ipxe.efi]]) on your web server, along with an iPXE [[:scripting|script]] containing the commands needed to boot the operating system.  For example, to boot a system comprising a Linux kernel and initial ramdisk, your script could contain
+Place your iPXE binary (e.g. [[http://boot.ipxe.org/ipxe.efi|ipxe.efi]]) on your web server, along with an iPXE [[:scripting|script]] containing the commands needed to boot your operating system.  For example, to boot a system comprising a Linux kernel and initial ramdisk, your script could contain
     #!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
@@ Line 55: / Line 55: @@
 ==== 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
-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.