Rebecca Cran 173a7a7daa OvmfPkg: Update build.sh to allow building OVMF then running QEMU 1 éve
..
8254TimerDxe a086f4a63b OvmfPkg: Use NestedInterruptTplLib in nested interrupt handlers 1 éve
8259InterruptControllerDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
AcpiPlatformDxe 935343cf16 OvmfPkg/AcpiPlatformDxe: Measure ACPI table from QEMU in TDVF 1 éve
AmdSev 1f9bd937b3 OvmfPkg/PlatformPei: Build GuidHob for Tdx measurement 1 éve
AmdSevDxe 466d8f65e3 OvmfPkg: Implement AcceptAllUnacceptedMemory in AmdSevDxe 1 éve
Bhyve f6e4824533 OvmfPkg: require self-signed PK when secure boot is enabled 1 éve
CloudHv f6e4824533 OvmfPkg: require self-signed PK when secure boot is enabled 1 éve
CompatImageLoaderDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
CpuHotplugSmm ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
CpuS3DataDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
Csm cdb80a281f OvmfPkg/LegacyBootManagerLib: Fix debug macro arguments 1 éve
EmuVariableFvbRuntimeDxe 2b20a34fd5 OvmfPkg-EmuVariableFvbRuntimeDxe: Support Access To Memory Above 4G 2 éve
EnrollDefaultKeys ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
Fdt b57911c84c OvmfPkg/FdtPciHostBridgeLib: io range is not mandatory 1 éve
Include 4d37059d8e OvmfPkg: Support Tdx measurement in OvmfPkgX64 1 éve
IncompatiblePciDeviceSupportDxe 18b5b14932 OvmfPkg/IncompatiblePciDeviceSupportDxe: Ignore OptionRom in Sev guest 1 éve
IntelTdx 9d669016d9 OvmfPkg/IntelTdx: Update README 1 éve
IoMmuDxe 47b9521513 OvmfPkg/IoMmuDxe: Add SEV support for reserved shared memory 1 éve
Library 019621d078 OvmfPkg/IntelTdx: Measure TdHob and Configuration FV in SecMain 1 éve
LinuxInitrdDynamicShellCommand ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
LocalApicTimerDxe a086f4a63b OvmfPkg: Use NestedInterruptTplLib in nested interrupt handlers 1 éve
LsiScsiDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
Microvm f6e4824533 OvmfPkg: require self-signed PK when secure boot is enabled 1 éve
MptScsiDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
PciHotPlugInitDxe 9e6b552b4c OvmfPkg/PciHotPlugInitDxe: reserve more mmio space 1 éve
PlatformCI 3beb8c9654 OvmfPkg/PlatformCI VS2019: Enable temporary workaround for cpuhp bugfix 1 éve
PlatformDxe 16acacf24c OvmfPkg: fix PlatformConfig 1 éve
PlatformPei 1f9bd937b3 OvmfPkg/PlatformPei: Build GuidHob for Tdx measurement 1 éve
PvScsiDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
QemuFlashFvbServicesRuntimeDxe 765ba5bf05 OvmfPkg/UefiCpuPkg: Add CcExit prefix to the APIs of CcExitLib 1 éve
QemuKernelLoaderFsDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
QemuRamfbDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
QemuVideoDxe 12e4043bd6 OvmfPkg/QemuVideoDxe/VbeShim.sh: remove end-of-options delimiter for nasm 1 éve
ResetVector 62044aa99b OvmfPkg/ResetVector: Removing SEV-ES CPUID bit check 1 éve
SataControllerDxe e87ac5ef49 OvmfPkg: Remove duplicated words 1 éve
Sec 6ea50514c1 OvmfPkg/OvmfPkgX64: Measure TdHob and Configuration FV in SecMain 1 éve
SioBusDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
SmbiosPlatformDxe 4cb94f20b0 OvmfPkg/SmbiosPlatformDxe: use PcdFirmware* 1 éve
SmmAccess ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
SmmControl2Dxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
Tcg b819388772 OvmfPkg: create Tcg12ConfigPei.inf 2 éve
TdxDxe 7dcc2f3870 OvmfPkg: Realize EdkiiMemoryAcceptProtocol in TdxDxe 1 éve
VirtNorFlashDxe e5ec3ba409 OvmfPkg/VirtNorFlashDxe: map flash memory as uncacheable 1 éve
Virtio10Dxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
VirtioBlkDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
VirtioFsDxe 3f282f4510 OvmfPkg/VirtioFsDxe: Check GetDriverName arguments 1 éve
VirtioGpuDxe b94836b224 OvmfPkg/VirtioGpuDxe: Check QueryMode arguments 1 éve
VirtioNetDxe f80580f56b OvmfPkg/VirtioNetDxe: Check ChildHandle argument in GetControllerName 1 éve
VirtioPciDeviceDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
VirtioRngDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
VirtioScsiDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
XenAcpiPlatformDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
XenBusDxe e87ac5ef49 OvmfPkg: Remove duplicated words 1 éve
XenIoPciDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
XenIoPvhDxe ac0a286f4d OvmfPkg: Apply uncrustify changes 2 éve
XenPlatformPei 0b633b1494 OvmfPkg/OvmfXen: Build platform info HOB in XenPlatformPei 1 éve
XenPvBlkDxe e87ac5ef49 OvmfPkg: Remove duplicated words 1 éve
XenResetVector 29280c7084 OvmfPkg/XenResetVector: Silent a warning from nasm 3 éve
License.txt 07a0f27b0e OvmfPkg/License.txt: refresh the MIT license text and include the SPDX ID 5 éve
OvmfPkg.ci.yaml ad6816c319 OvmfPkg: Do not check VbeShim.h formatting with Uncrustify 2 éve
OvmfPkg.dec d3109e5f18 OvmfPkg/IntelTdx: Add TdxHelperLibNull 1 éve
OvmfPkgIa32.dsc f6e4824533 OvmfPkg: require self-signed PK when secure boot is enabled 1 éve
OvmfPkgIa32.fdf d452feedf2 OvmfPkg: raise DXEFV size to 13 MB in the traditional platform FDFs 1 éve
OvmfPkgIa32X64.dsc f6e4824533 OvmfPkg: require self-signed PK when secure boot is enabled 1 éve
OvmfPkgIa32X64.fdf d452feedf2 OvmfPkg: raise DXEFV size to 13 MB in the traditional platform FDFs 1 éve
OvmfPkgX64.dsc f6e4824533 OvmfPkg: require self-signed PK when secure boot is enabled 1 éve
OvmfPkgX64.fdf 4d37059d8e OvmfPkg: Support Tdx measurement in OvmfPkgX64 1 éve
OvmfTpmDxe.fdf.inc 4de8d61bce OvmfPkg: rework TPM configuration 2 éve
OvmfTpmPei.fdf.inc 4de8d61bce OvmfPkg: rework TPM configuration 2 éve
OvmfXen.dsc ae80fe997d Revert "OvmfPkg: Add CpuPageTableLib required by MpInitLib." 1 éve
OvmfXen.fdf 1ef86f1201 mv OvmfPkg: move fdf include snippets to Include/Fdf 1 éve
OvmfXenElfHeaderGenerator.c b909b4ad09 OvmfPkg: Make the Xen ELF header generator more flexible 2 éve
README 316e6df435 OvmfPkg: Add reference to new build instructions 1 éve
build.sh 173a7a7daa OvmfPkg: Update build.sh to allow building OVMF then running QEMU 1 éve

README


=== OVMF OVERVIEW ===

The Open Virtual Machine Firmware (OVMF) project aims
to support firmware for Virtual Machines using the edk2
code base. More information can be found at:

http://www.tianocore.org/ovmf/

=== STATUS ===

Current capabilities:
* IA32 and X64 architectures
* QEMU (version 1.7.1 or later, with 1.7 or later machine types)
- Video, keyboard, IDE, CD-ROM, serial
- Runs UEFI shell
- Optional NIC support.
* UEFI Linux boots
* UEFI Windows 8 boots
* UEFI Windows 7 & Windows 2008 Server boot (see important notes below!)

=== FUTURE PLANS ===

* Test/Stabilize UEFI Self-Certification Tests (SCT) results

=== BUILDING OVMF ===

Pre-requisites:
* Build environment capable of build the edk2 MdeModulePkg.
* A properly configured ASL compiler:
- Intel ASL compiler: Available from http://www.acpica.org
- Microsoft ASL compiler: Available from http://www.acpi.info
* NASM: http://www.nasm.us/

Update Conf/target.txt ACTIVE_PLATFORM for OVMF:
PEI arch DXE arch UEFI interfaces
* OvmfPkg/OvmfPkgIa32.dsc IA32 IA32 IA32
* OvmfPkg/OvmfPkgIa32X64.dsc IA32 X64 X64
* OvmfPkg/OvmfPkgX64.dsc X64 X64 X64

Update Conf/target.txt TARGET_ARCH based on the .dsc file:
TARGET_ARCH
* OvmfPkg/OvmfPkgIa32.dsc IA32
* OvmfPkg/OvmfPkgIa32X64.dsc IA32 X64
* OvmfPkg/OvmfPkgX64.dsc X64

Following the edk2 build process, you will find the OVMF binaries
under the $WORKSPACE/Build/*/*/FV directory. The actual path will
depend on how your build is configured. You can expect to find
these binary outputs:
* OVMF.FD
- Please note! This filename has changed. Older releases used OVMF.Fv.
* OvmfVideo.rom
- This file is not built separately any longer, starting with svn r13520.

If you are new to building in edk2 or looking for the latest build
instructions, visit https://github.com/tianocore/tianocore.github.io/wiki/Build-Instructions

More OVMF-specific build information can be found at:

https://github.com/tianocore/tianocore.github.io/wiki/How%20to%20build%20OVMF

=== RUNNING OVMF on QEMU ===

* Be sure to use qemu-system-x86_64, if you are using an X64 firmware.
(qemu-system-x86_64 works for the IA32 firmware as well, of course.)
* Use OVMF for QEMU firmware (3 options available)
- Option 1: Use QEMU -pflash parameter
* QEMU/OVMF will use emulated flash, and fully support UEFI variables
* Run qemu with: -pflash path/to/OVMF.fd
* Note that this option is required for running SecureBoot-enabled builds
(-D SECURE_BOOT_ENABLE).
- Option 2: Use QEMU -bios parameter
* Note that UEFI variables will be partially emulated, and non-volatile
variables may lose their contents after a reboot
* Run qemu with: -bios path/to/OVMF.fd
- Option 3: Use QEMU -L parameter
* Note that UEFI variables will be partially emulated, and non-volatile
variables may lose their contents after a reboot
* Either copy, rename or symlink OVMF.fd => bios.bin
* Use the QEMU -L parameter to specify the directory where the bios.bin
file is located.
* The EFI shell is built into OVMF builds at this time, so it should
run automatically if a UEFI boot application is not found on the
removable media.
* On Linux, newer version of QEMU may enable KVM feature, and this might
cause OVMF to fail to boot. The QEMU '-no-kvm' may allow OVMF to boot.
* Capturing OVMF debug messages on qemu:
- The default OVMF build writes debug messages to IO port 0x402. The
following qemu command line options save them in the file called
debug.log: '-debugcon file:debug.log -global isa-debugcon.iobase=0x402'.
- It is possible to revert to the original behavior, when debug messages were
written to the emulated serial port (potentially intermixing OVMF debug
output with UEFI serial console output). For this the
'-D DEBUG_ON_SERIAL_PORT' option has to be passed to the build command (see
the next section), and in order to capture the serial output qemu needs to
be started with eg. '-serial file:serial.log'.
- Debug messages fall into several categories. Logged vs. suppressed
categories are controlled at OVMF build time by the
'gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel' bitmask (an UINT32
value) in the selected .dsc file. Individual bits of this bitmask are
defined in . One non-default bit (with
some performance impact) that is frequently set for debugging is 0x00400000
(DEBUG_VERBOSE).
- The RELEASE build target ('-b RELEASE' build option, see below) disables
all debug messages. The default build target is DEBUG.

=== Build Scripts ===

On systems with the bash shell you can use OvmfPkg/build.sh to simplify
building and running OVMF.

So, for example, to build + run OVMF X64:
$ OvmfPkg/build.sh -a X64
$ OvmfPkg/build.sh -a X64 qemu

And to run a 64-bit UEFI bootable ISO image:
$ OvmfPkg/build.sh -a X64 qemu -cdrom /path/to/disk-image.iso

To build a 32-bit OVMF without debug messages using GCC 4.8:
$ OvmfPkg/build.sh -a IA32 -b RELEASE -t GCC48

=== SMM support ===

Requirements:
* SMM support requires QEMU 2.5.
* The minimum required QEMU machine type is "pc-q35-2.5".
* SMM with KVM requires Linux 4.4 (host).

OVMF is capable of utilizing SMM if the underlying QEMU or KVM hypervisor
emulates SMM. SMM is put to use in the S3 suspend and resume infrastructure,
and in the UEFI variable driver stack. The purpose is (virtual) hardware
separation between the runtime guest OS and the firmware (OVMF), with the
intent to make Secure Boot actually secure, by preventing the runtime guest OS
from tampering with the variable store and S3 areas.

For SMM support, OVMF must be built with the "-D SMM_REQUIRE" option. The
resultant firmware binary will check if QEMU actually provides SMM emulation;
if it doesn't, then OVMF will log an error and trigger an assertion failure
during boot (even in RELEASE builds). Both the naming of the flag (SMM_REQUIRE,
instead of SMM_ENABLE), and this behavior are consistent with the goal
described above: this is supposed to be a security feature, and fallbacks are
not allowed. Similarly, a pflash-backed variable store is a requirement.

QEMU should be started with the options listed below (in addition to any other
guest-specific flags). The command line should be gradually composed from the
hints below. '\' is used to extend the command line to multiple lines, and '^'
can be used on Windows.

* QEMU binary and options specific to 32-bit guests:

$ qemu-system-i386 -cpu coreduo,-nx \

or

$ qemu-system-x86_64 -cpu ,-lm,-nx \

* QEMU binary for running 64-bit guests (no particular options):

$ qemu-system-x86_64 \

* Flags common to all SMM scenarios (only the Q35 machine type is supported):

-machine q35,smm=on,accel=(tcg|kvm) \
-m ... \
-smp ... \
-global driver=cfi.pflash01,property=secure,value=on \
-drive if=pflash,format=raw,unit=0,file=OVMF_CODE.fd,readonly=on \
-drive if=pflash,format=raw,unit=1,file=copy_of_OVMF_VARS.fd \

* In order to disable S3, add:

-global ICH9-LPC.disable_s3=1 \

=== Network Support ===

OVMF provides a UEFI network stack by default. Its lowest level driver is the
NIC driver, higher levels are generic. In order to make DHCP, PXE Boot, and eg.
socket test utilities from the StdLib edk2 package work, (1) qemu has to be
configured to emulate a NIC, (2) a matching UEFI NIC driver must be available
when OVMF boots.

(If a NIC is configured for the virtual machine, and -- dependent on boot order
-- PXE booting is attempted, but no DHCP server responds to OVMF's DHCP
DISCOVER message at startup, the boot process may take approx. 3 seconds
longer.)

* For each NIC emulated by qemu, a GPLv2 licensed UEFI driver is available from
the iPXE project. The qemu source distribution contains prebuilt binaries of
these drivers (and of course allows one to rebuild them from source as well).
This is the recommended set of drivers.

* Use the qemu -netdev and -device options, or the legacy -net option, to
enable NIC support: .

* The iPXE drivers are automatically available to and configured for OVMF in
the default qemu installation.

* Independently of the iPXE NIC drivers, the default OVMF build provides a
basic virtio-net driver, located in OvmfPkg/VirtioNetDxe.

* Also independently of the iPXE NIC drivers, Intel's proprietary E1000 NIC
driver (from the BootUtil distribution) can be embedded in the OVMF image at
build time:

- Download BootUtil:
- Navigate to
https://downloadcenter.intel.com/download/19186/Ethernet-Intel-Ethernet-Connections-Boot-Utility-Preboot-Images-and-EFI-Drivers
- Click the download link for "PREBOOT.EXE".
- Accept the Intel Software License Agreement that appears.
- Unzip "PREBOOT.EXE" into a separate directory (this works with the
"unzip" utility on platforms different from Windows as well).
- Copy the "APPS/EFI/EFIx64/E3522X2.EFI" driver binary to
"Intel3.5/EFIX64/E3522X2.EFI" in your WORKSPACE.
- Intel have stopped distributing an IA32 driver binary (which used to
match the filename pattern "E35??E2.EFI"), thus this method will only
work for the IA32X64 and X64 builds of OVMF.

- Include the driver in OVMF during the build:
- Add "-D E1000_ENABLE" to your build command (only when building
"OvmfPkg/OvmfPkgIa32X64.dsc" or "OvmfPkg/OvmfPkgX64.dsc").
- For example: "build -D E1000_ENABLE".

* When a matching iPXE driver is configured for a NIC as described above, it
takes priority over other drivers that could possibly drive the card too:

| e1000 ne2k_pci pcnet rtl8139 virtio-net-pci
---------------------+------------------------------------------------
iPXE | x x x x x
VirtioNetDxe | x
Intel BootUtil (X64) | x

=== HTTPS Boot ===

HTTPS Boot is an alternative solution to PXE. It replaces the tftp server
with a HTTPS server so the firmware can download the images through a trusted
and encrypted connection.

* To enable HTTPS Boot, you have to build OVMF with -D NETWORK_HTTP_BOOT_ENABLE
and -D NETWORK_TLS_ENABLE. The former brings in the HTTP stack from
NetworkPkg while the latter enables TLS support in both NetworkPkg and
CryptoPkg.

If you want to exclude the unsecured HTTP connection completely, OVMF has to
be built with -D NETWORK_ALLOW_HTTP_CONNECTIONS=FALSE so that only the HTTPS
connections will be accepted.

* By default, there is no trusted certificate. The user has to import the
certificates either manually with "Tls Auth Configuration" utility in the
firmware UI or through the fw_cfg entry, etc/edk2/https/cacerts.

-fw_cfg name=etc/edk2/https/cacerts,file=

The blob for etc/edk2/https/cacerts has to be in the format of Signature
Database(*1). You can use p11-kit(*2) or efisiglit(*3) to create the
certificate list.

If you want to create the certificate list based on the CA certificates
in your local host, p11-kit will be a good choice. Here is the command to
create the list:

p11-kit extract --format=edk2-cacerts --filter=ca-anchors \
--overwrite --purpose=server-auth

If you only want to import one certificate, efisiglist is the tool for you:

efisiglist -a -o

Please note that the certificate has to be in the DER format.

You can also append a certificate to the existing list with the following
command:

efisiglist -i -a -o

NOTE: You may need the patch to make efisiglist generate the correct header.
(https://github.com/rhboot/pesign/pull/40)

* Besides the trusted certificates, it's also possible to configure the trusted
cipher suites for HTTPS through another fw_cfg entry: etc/edk2/https/ciphers.

OVMF expects a binary UINT16 array which comprises the cipher suites HEX
IDs(*4). If the cipher suite list is given, OVMF will choose the cipher
suite from the intersection of the given list and the built-in cipher
suites. Otherwise, OVMF just chooses whatever proper cipher suites from the
built-in ones.

- Using QEMU 5.2 or later, QEMU can expose the ordered list of permitted TLS
cipher suites from the host side to OVMF:

-object tls-cipher-suites,id=mysuite0,priority=@SYSTEM \
-fw_cfg name=etc/edk2/https/ciphers,gen_id=mysuite0

(Refer to the QEMU manual and to
for more
information on the "priority" property.)

- Using QEMU 5.1 or earlier, the array has to be passed from a file:

-fw_cfg name=etc/edk2/https/ciphers,file=

whose contents can be generated with the following script, for example:

export LC_ALL=C
openssl ciphers -V \
| sed -r -n \
-e 's/^ *0x([0-9A-F]{2}),0x([0-9A-F]{2}) - .*$/\\\\x\1 \\\\x\2/p' \
| xargs -r -- printf -- '%b' > ciphers.bin

This script creates ciphers.bin that contains all the cipher suite IDs
supported by openssl according to the local host configuration.

You may want to enable only a limited set of cipher suites. Then, you
should check the validity of your list first:

openssl ciphers -V

If all the cipher suites in your list map to the proper HEX IDs, go ahead
to modify the script and execute it:

export LC_ALL=C
openssl ciphers -V \
| sed -r -n \
-e 's/^ *0x([0-9A-F]{2}),0x([0-9A-F]{2}) - .*$/\\\\x\1 \\\\x\2/p' \
| xargs -r -- printf -- '%b' > ciphers.bin

(*1) See "31.4.1 Signature Database" in UEFI specification 2.7 errata A.
(*2) p11-kit: https://github.com/p11-glue/p11-kit/
(*3) efisiglist: https://github.com/rhboot/pesign/blob/master/src/efisiglist.c
(*4) https://wiki.mozilla.org/Security/Server_Side_TLS#Cipher_names_correspondence_table

=== OVMF Flash Layout ===

Like all current IA32/X64 system designs, OVMF's firmware device (rom/flash)
appears in QEMU's physical address space just below 4GB (0x100000000).

OVMF supports building a 1MB, 2MB or 4MB flash image (see the DSC files for the
FD_SIZE_1MB, FD_SIZE_2MB, FD_SIZE_4MB build defines). The base address for the
1MB image in QEMU physical memory is 0xfff00000. The base address for the 2MB
image is 0xffe00000. The base address for the 4MB image is 0xffc00000.

Using the 1MB or 2MB image, the layout of the firmware device in memory looks
like:

+--------------------------------------- 4GB (0x100000000)
| VTF0 (16-bit reset code) and OVMF SEC
| (SECFV, 208KB/0x34000)
+--------------------------------------- varies based on flash size
|
| Compressed main firmware image
| (FVMAIN_COMPACT)
|
+--------------------------------------- base + 0x20000
| Fault-tolerant write (FTW)
| Spare blocks (64KB/0x10000)
+--------------------------------------- base + 0x10000
| FTW Work block (4KB/0x1000)
+--------------------------------------- base + 0x0f000
| Event log area (4KB/0x1000)
+--------------------------------------- base + 0x0e000
| Non-volatile variable storage
| area (56KB/0xe000)
+--------------------------------------- base address

Using the 4MB image, the layout of the firmware device in memory looks like:

+--------------------------------------- base + 0x400000 (4GB/0x100000000)
| VTF0 (16-bit reset code) and OVMF SEC
| (SECFV, 208KB/0x34000)
+--------------------------------------- base + 0x3cc000
|
| Compressed main firmware image
| (FVMAIN_COMPACT, 3360KB/0x348000)
|
+--------------------------------------- base + 0x84000
| Fault-tolerant write (FTW)
| Spare blocks (264KB/0x42000)
+--------------------------------------- base + 0x42000
| FTW Work block (4KB/0x1000)
+--------------------------------------- base + 0x41000
| Event log area (4KB/0x1000)
+--------------------------------------- base + 0x40000
| Non-volatile variable storage
| area (256KB/0x40000)
+--------------------------------------- base address (0xffc00000)

The code in SECFV locates FVMAIN_COMPACT, and decompresses the
main firmware (MAINFV) into RAM memory at address 0x800000. The
remaining OVMF firmware then uses this decompressed firmware
volume image.

=== UEFI Windows 7 & Windows 2008 Server ===

* One of the '-vga std' and '-vga qxl' QEMU options should be used.
* Only one video mode, 1024x768x32, is supported at OS runtime.
* The '-vga qxl' QEMU option is recommended. After booting the installed
guest OS, select the video card in Device Manager, and upgrade its driver
to the QXL XDDM one. Download location:
, Guest | Windows binaries.
This enables further resolutions at OS runtime, and provides S3
(suspend/resume) capability.