On Thu, 28 Oct 2021 07:46:11 -0600 dann frazier <da...@dannf.org> wrote:
> severity 997913 wishlist > thanks > > On Tue, Oct 26, 2021 at 07:31:38PM -0500, Glenn Washburn wrote: > > Package: ovmf-ia32 > > Version: 2020.11-4 > > > > Hello Maintainers, > > > > I'd like ovmf-ia32 to install a file useable by QEMU's -bios option. > > Currently the package only installs OVMF32_CODE_4M.secboot.fd and > > OVMF32_VARS_4M.fd, but I believe I need a file that combines both code > > and vars. According to the wiki[1], I believe I can use the existing > > files using "-drive if=pflash,..." options, but that is not a great > > option for me. > > Can you elaborate more on your use case? While we do provide such an > image for X64, that is for backwards-compatibility only. I'm working on GRUB2's test suite and it has tests that use QEMU for many of its tests. Specifically, I need the combined firmware file when testing the i386-efi target. Perhaps, I don't need a binary with combined code and vars. On the ARM and ARM64 EFI targets, I can pass the AAVMF32_CODE.fd to -bios just fine. So perhaps the IA32 firmware is built in such a way that the code file requires the vars, but could be build to not require it? IOW, why can't I just send the firmware CODE file to QEMU using -bios like I can with ARM and ARM64? Also, I don't need the secure boot feature of the firmware. The wiki leaves me with the suspicion that I may need to configure some of the firmware variables before I can boot successfully. Perhaps that would only be the case if I were wanting to boot with secure boot enabled. I'm also curious about the 4M in the file name. My guess is that it indicates a build option. Could this be part of the equation? Glenn
