Hi,
A patch such as the attached (to avoid potential line wrap) one, which
changes debian/rules to:
* add an entry to OVMF32_IMAGES;
* perform a small copy-paste-modify job in the target which depends on
OVMF32_BINARIES and OVMF32_IMAGES
seems to be enough to build and package a non-secboot
Hi,
I hit this issue when testing a bugfix for memtest86+ under QEMU.
Before finding this bug report, I worked around it by taking OVMF
non-secboot binaries from an Arch package, but I agree with Alain:
non-secboot binaries are useful, and besides, multiple (most ?) other
distros provide them
Package: ovmf-ia32
Version: 2020.11-2+deb11u1
Hi,
Recently I wanted to analyze behavior of a 32-bit EFI OS bootfile, and
wanted to setup a KVM with 32 bit UEFI to do this.
However, qemu/kvm apparently does not (yet) support .secboot.fd UEFI
images, but these are the only ones available in
3 matches
Mail list logo
