Solution: OVMF 4M-based VMs broken after updating to F39

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I had an EFI VM that was configured to use
/usr/share/edk2/ovmf-4m/OVMF_CODE.secboot.fd as its bootloader in F38.

The edk2-ovmf package in F39 no longer installs it. This results in an error message starting any VM that uses OVMF 4M images.

The /usr/share/edk2/ovmf-4m directory no longer exists, and /usr/share/edk2/ovmf had the following contents in F39:

-rw-r--r--. 1 root root 3678208 Oct 10 20:00 OVMF_CODE_4M.qcow2
-rw-r--r--. 1 root root    1484 Oct 10 20:00 OVMF_CODE_4M.secboot.pcr
-rw-r--r--. 1 root root 3678208 Oct 10 20:00 OVMF_CODE_4M.secboot.qcow2

There was nothing with "4M" and ".fd" in it,

So, I manually edited the XML VM config, but neither OVMF_CODE_4M.secboot.qcow2 nor OVMF_CODE_4M.secboot.pcr worked. Attempting to boot OVMF_CODE_4M.secboot.qcow2 appeared to be the most promising approach except that it failed with a cryptic error message referencing qcow2 format and the flash file.

My existing flash file was:

/var/lib/libvirt/qemu/nvram/WINDOWS10-EFI_VARS.fd

After doing some digging I found the solution:

qemu-img convert -f raw -O qcow2 WINDOWS10-EFI_VARS.fd WINDOWS10-EFI_VARS.qcow2

This converted the emulated nvram storage file, apparently, from raw block format to qcow2. With that, the VM started successfully. For reference, my final settings were:

<loader readonly="yes" secure="yes" type="pflash" format="qcow2">/usr/share/edk2/ovmf/OVMF_CODE_4M.secboot.qcow2</loader> <nvram template="/usr/share/edk2/ovmf/OVMF_VARS_4M.secboot.qcow2" format="qcow2">/var/lib/libvirt/qemu/nvram/WINDOWS10-EFI_VARS.qcow2</nvram>

There used to be release notes packaged with each release that were called "Common F# bugs", or something like that. They listed common upgrade issues. Not sure where it is these days, a brief search didn't find them. This should be mentioned there, wherever it is…
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux