OVMF (Open Virtual Machine Firmware) is a project that aim is to enable UEFI support in various virutal machines. According to whitepaper various projects have interest in supporting OVFM ie. VirtualBox, Xen, BHyVe and of course QEMU. Why someone may be interested in OVMF ?
IMHO the most important reason is that OVMF give ability to develop UEFI applications without using real hardware. This speeds up development cycle by giving ability to start before hardware prototype arrive. There are also cases when hardware is available only remotely, dealing with remote setup is usually annoying, so part of development can be performed locally.
It also improve testing and debugging, because we have full control over execution environment internals. Error injection and corner case analysis can be ineffective in real world. OVMF and qemu open debugging to new levels.
It enables training and learning environment. Not every one can obtain UEFI PC and mess with it when there is risk of destroying sth.
Many other reason like ability to test/develop UEFI support for various OSes, simplified debugging, lack of dependencies on legacy address space and devices. This and other interesting reasons can be found in Laszlo Ersek whitepaper
What I want to show below is procedure for setting up development environment
for UEFI applications and show how to compile and deploy
application in that environment.
Let’s use upstream version of QEMU:
1 2 3 4 5 6
git clone https://github.com/qemu/qemu.git cd qemu git submodule init git submodule update ./configure --target-list=x86_64-softmmu make -j$(nproc)
Prepare application image
Of course size depends on you application requirements. Usually 128MB is way too much.
1 2 3
dd if=/dev/zero of=app.disk bs=1 count=1 seek=$(( (128 * 1024 * 1024) - 1)) sudo mkfs.vfat app.disk cd ..
First build UEFI firmware with shell:
1 2 3 4
git clone https://github.com/tianocore/edk2.git cd edk2 nice OvmfPkg/build.sh -a X64 -n $(nproc) cp Build/OvmfX64/DEBUG_GCC4?/FV/OVMF.fd ovmf.flash
Now we need some application that can be delivered over
app.disk to virtual
machine. There are couple examples of UEFI applications in
edk2 source code,
but let’s start with classical
Hello World. Source code can be found in
MdeModulePkg/Application/HelloWorld. This module is built in
because of that we can built it as follows:
source edksetup.sh build -a X64 -p MdeModulePkg/MdeModulePkg.dsc -t GCC49 -n$(nproc)
Let’s put it into
1 2 3 4 5
mkdir mnt_app cp ../qemu/app.disk . sudo mount app.disk mnt_app sudo cp Build/MdeModule/DEBUG_GCC49/X64/HelloWorld.efi mnt_app sudo umount mnt_app
When we develop UEFI application best way would be to run OVMF to UEFI Shell for test purposes. This is not default option. How to change boot order so we every time will lend in shell ?
On booting screen hit
You should be in main menu of UEFI setup:
Boot Maintenance Manager -> Boot Options -> Change Boot Order,
Change Boot Order and hit
<Enter>. Then using
+/- keys move
EFI Internal Shell to the top.
Do not forget to save configuration with
To boot OVMF I’m using Laszlo’s slightly modified script which can be found here.
After booting to UEFI Shell we should look something like this:
FS0: in mapping table list - this is our
Result should look like this:
NOTE: If your result is different then make sure to check last lines of
app.ovmf.log it can give you some hints.
Hopefully at least part of above article was useful somehow. There are many ways to extend this sample presentation. In example application delivery can be achieved by network transfer. If you have any question or need UEFI support please do not bother to ping me in comments or using any other medium.