OvmfPkg/README

   1
   2 === OVMF OVERVIEW ===
   3
   4 The Open Virtual Machine Firmware (OVMF) project aims
   5 to support firmware for Virtual Machines using the edk2
   6 code base.  More information can be found at:
   7
   8 http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF
   9
  10 === STATUS ===
  11
  12 Current status: Alpha
  13
  14 Current capabilities:
  15 * IA32 and X64 architectures
  16 * QEMU (0.10.0 or later)
  17   - Video, keyboard, IDE, CD-ROM, serial
  18   - Runs UEFI shell
  19   - Optional NIC support.  Requires QEMU (0.12.2 or later)
  20 * UEFI Linux boots
  21 * UEFI Windows 8 boots
  22
  23 === FUTURE PLANS ===
  24
  25 * Stabilize UEFI Linux boot
  26 * Test/Stabilize UEFI Self-Certification Tests (SCT) results
  27
  28 === BUILDING OVMF ===
  29
  30 Pre-requisites:
  31 * Build environment capable of build the edk2 MdeModulePkg.
  32 * A properly configured ASL compiler:
  33   - Intel ASL compiler: Available from http://www.acpica.org
  34   - Microsoft ASL compiler: Available from http://www.acpi.info
  35
  36 Update Conf/target.txt ACTIVE_PLATFORM for OVMF:
  37                              PEI arch   DXE arch   UEFI interfaces
  38 * OvmfPkg/OvmfPkgIa32.dsc      IA32       IA32           IA32
  39 * OvmfPkg/OvmfPkgIa32X64.dsc   IA32       X64            X64
  40 * OvmfPkg/OvmfPkgX64.dsc       X64        X64            X64
  41
  42 Update Conf/target.txt TARGET_ARCH based on the .dsc file:
  43                              TARGET_ARCH
  44 * OvmfPkg/OvmfPkgIa32.dsc     IA32
  45 * OvmfPkg/OvmfPkgIa32X64.dsc  IA32 X64
  46 * OvmfPkg/OvmfPkgX64.dsc      X64
  47
  48 Following the edk2 build process, you will find the OVMF binaries
  49 under the $WORKSPACE/Build/*/*/FV directory.  The actual path will
  50 depend on how your build is configured.  You can expect to find
  51 these binary outputs:
  52 * OVMF.FD
  53   - Please note!  This filename has changed.  Older releases used OVMF.Fv.
  54 * OvmfVideo.rom
  55   - This file is not built separately any longer, starting with svn r13520.
  56
  57 More information on building OVMF can be found at:
  58
  59 http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVMF
  60
  61 === RUNNING OVMF on QEMU ===
  62
  63 * QEMU 0.9.1 or later is required.
  64 * Either copy, rename or symlink OVMF.FD => bios.bin
  65 * Be sure to use qemu-system-x86_64, if you are using and X64 firmware.
  66   (qemu-system-x86_64 works for the IA32 firmware as well, of course.)
  67 * Use the QEMU -L parameter to specify the directory where the bios.bin
  68   file is located.
  69 * The EFI shell is built into OVMF builds at this time, so it should
  70   run automatically if a UEFI boot application is not found on the
  71   removable media.
  72 * On Linux, newer version of QEMU may enable KVM feature, and this might
  73   cause OVMF to fail to boot.  The QEMU '-no-kvm' may allow OVMF to boot.
  74 * Capturing OVMF debug messages on qemu:
  75   - The default OVMF build writes debug messages to IO port 0x402.  The
  76     following qemu command line options save them in the file called
  77     debug.log: '-debugcon file:debug.log -global isa-debugcon.iobase=0x402'.
  78   - It is possible to revert to the original behavior, when debug messages were
  79     written to the emulated serial port (potentially intermixing OVMF debug
  80     output with UEFI serial console output).  For this the
  81     '-D DEBUG_ON_SERIAL_PORT' option has to be passed to the build command (see
  82     the next section), and in order to capture the serial output qemu needs to
  83     be started with eg. '-serial file:serial.log'.
  84   - Debug messages fall into several categories.  Logged vs. suppressed
  85     categories are controlled at OVMF build time by the
  86     'gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel' bitmask (an UINT32
  87     value) in the selected .dsc file.  Individual bits of this bitmask are
  88     defined in <MdePkg/Include/Library/DebugLib.h>.  One non-default bit (with
  89     some performance impact) that is frequently set for debugging is 0x00400000
  90     (DEBUG_VERBOSE).
  91   - The RELEASE build target ('-b RELEASE' build option, see below) disables
  92     all debug messages.  The default build target is DEBUG.
  93
  94 === Build Scripts ===
  95
  96 On systems with the bash shell you can use OvmfPkg/build.sh to simplify
  97 building and running OVMF.
  98
  99 So, for example, to build + run OVMF X64:
 100 $ OvmfPkg/build.sh -a X64
 101 $ OvmfPkg/build.sh -a X64 qemu
 102
 103 And to run a 64-bit UEFI bootable ISO image:
 104 $ OvmfPkg/build.sh -a X64 qemu -cdrom /path/to/disk-image.iso
 105
 106 To build a 32-bit OVMF without debug messages using GCC 4.5:
 107 $ OvmfPkg/build.sh -a IA32 -b RELEASE -t GCC45
 108
 109 === Network Support ===
 110
 111 To add network drivers to OVMF:
 112
 113 * Download UEFI drivers for the e1000 NIC
 114   - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17515&lang=eng
 115   - Install the drivers into a directory called Intel3.5 in your WORKSPACE
 116
 117 * Include the drivers in OVMF during the build:
 118   - Add '-D NETWORK_ENABLE' to your build command
 119   - For example: build -D NETWORK_ENABLE
 120
 121 * Use the QEMU -net parameter to enable NIC support.
 122   - QEMU does not support UEFI DHCP or UEFI PXE Boot, so long timeouts will
 123     occur when NICs are enabled.  The long timeouts can be avoided by
 124     interrupts the boot sequence by pressing a key when the logo appears.
 125   - Example: Enable e1000 NIC with a DHCP server and restrict packet
 126     forwarding:
 127     -net nic,model=e1000 -net user,restrict=yes -net user,dhcpstart=10.0.2.10
 128   - Example: Enable e1000 NIC with a DHCP server, restrict packet forwarding,
 129     and generate PCAP file:
 130     -net nic,model=e1000 -net user,restrict=yes -net user,dhcpstart=10.0.2.10
 131     -net dump,file=a.pcap
 132   - Example: Enable 2 e1000 NICs with a DHCP server and restrict
 133     packet forwarding:
 134     -net nic,model=e1000,addr=3 -net nic,model=e1000,addr=4
 135     -net user,restrict=yes -net user,dhcpstart=10.0.2.10
 136
 137 === UNIXGCC Debug ===
 138
 139 If you build with the UNIXGCC toolchain, then debugging will be disabled
 140 due to larger image sizes being produced by the UNIXGCC toolchain. The
 141 first choice recommendation is to use GCC44 or newer instead.
 142
 143 If you must use UNIXGCC, then you can override the build options for
 144 particular libraries and modules in the .dsc to re-enable debugging
 145 selectively. For example:
 146   [Components]
 147   OvmfPkg/Library/PlatformBdsLib/PlatformBdsLib.inf {
 148     <BuildOptions>
 149       GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG
 150   }
 151   IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe.inf {
 152     <BuildOptions>
 153       GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG
 154   }
 155