Package: ovmf Version: 2020.08-1 Severity: normal Control: block 973780 by -1
Dear Maintainer, When I start QEMU as cp /usr/share/OVMF/OVMF_VARS_4M.fd /tmp/efivars.fd qemu-system-x86_64 -net nic,model=virtio -net user \ -object rng-random,filename=/dev/urandom,id=rng0 \ -device virtio-rng-pci,rng=rng0,id=rng-device0 \ -drive file=/var/tmp/debian-bullseye-amd64.img,if=virtio,index=0,format=raw \ -drive if=pflash,format=raw,read-only,file=/usr/share/OVMF/OVMF_CODE_4M.fd \ -drive if=pflash,format=raw,file=/tmp/efivars.fd -m 1024 \ -machine q35,smm=on -global driver=cfi.pflash01,property=secure,value=on \ -cpu max -enable-kvm The QEMU image debian-bullseye-amd64 starts fine. But if I replace OVMF_CODE_4M to OVMD_CODE_4M.ms.fd and OVMD_VARS_4M.fd to OVMF_VARS_4M.fd, then no BIOS screen shows up. When I built an i386 UEFI secure boot ROM at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973571#61 UEFI shell showed up. I wonder if something wrong in OVMF_VARS_4M.ms.fd... Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
