to support firmware for Virtual Machines using the edk2\r
code base. More information can be found at:\r
\r
- https://edk2.tianocore.org/OVMF.html\r
+http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF\r
\r
=== STATUS ===\r
\r
under the $WORKSPACE/Build/*/*/FV directory. The actual path will\r
depend on how your build is configured. You can expect to find\r
these binary outputs:\r
-* OVMF.fd \r
+* OVMF.Fv\r
+ * Please note! This filename has changed. Older releases used OVMF.fd.\r
* CirrusLogic5446.rom\r
\r
More information on building OVMF can be found at:\r
-* https://edk2.tianocore.org/build-ovmf.html\r
+\r
+http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVMF\r
\r
=== RUNNING OVMF on QEMU ===\r
\r
* QEMU 0.9.1 or later is required.\r
-* Either copy, rename or symlink OVMF.fd => bios.bin\r
+* Either copy, rename or symlink OVMF.Fv => bios.bin\r
* Either copy, rename or symlink CirrusLogic5446.rom => vgabios-cirrus.bin\r
* Be sure to use qemu-system-x86_64, if you are using and X64 firmware.\r
(qemu-system-x86_64 works for the IA32 firmware as well, of course.)\r
* The EFI shell is built into OVMF builds at this time, so it should\r
run automatically if a UEFI boot application is not found on the\r
removable media.\r
+* On Linux, newer version of QEMU may enable KVM feature, and this might cause OVMF\r
+ to fail to boot. The QEMU '-no-kvm' may allow OVMF to boot.\r
\r