https://bugzilla.suse.com/show_bug.cgi?id=1216472 https://bugzilla.suse.com/show_bug.cgi?id=1216472#c3 Vasily Ulyanov <vasily.ulyanov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(vasily.ulyanov@su | |se.com) | --- Comment #3 from Vasily Ulyanov <vasily.ulyanov@suse.com> --- (In reply to Joey Lee from comment #1)

I can not reproduce this issue on my local machine with qemu-ovmf + secure boot.

My code/vars are:

<loader readonly='yes' secure='no' type='pflash'>/usr/share/qemu/ovmf-x86_64-code.bin</loader> <nvram template='/usr/share/qemu/ovmf-x86_64-vars.bin'>/var/lib/libvirt/qemu/nvram/ opensuseTW_VARS.fd</nvram>

I guess with `secure='no'` the VM will run **without** Secure Boot, right? This works fine for me as well. The issue is observed when `secure='yes'` and `ovmf-x86_64-smm-ms-code.bin` is used. I will grab the full domxml from the test run and attach it here.

Do you know where are OVMF_CODE.secboot.fd and OVMF_VARS.secboot.fd from?

Those are just symlinks to `/usr/share/qemu/ovmf-x86_64-smm-ms-code.bin` and `/usr/share/qemu/ovmf-x86_64-smm-ms-vars.bin`: qemu@testvmi:/> ls -la /usr/share/OVMF/OVMF_CODE.secboot.fd lrwxrwxrwx 1 root root 35 Nov 1 01:52 /usr/share/OVMF/OVMF_CODE.secboot.fd -> ../qemu/ovmf-x86_64-smm-ms-code.bin qemu@testvmi:/> qemu@testvmi:/> ls -la /usr/share/OVMF/OVMF_VARS.secboot.fd lrwxrwxrwx 1 root root 35 Nov 1 01:52 /usr/share/OVMF/OVMF_VARS.secboot.fd -> ../qemu/ovmf-x86_64-smm-ms-vars.bin qemu@testvmi:/> qemu@testvmi:/> rpm -qa | grep ovmf qemu-ovmf-x86_64-202308-Virt.1699.256.44.noarc -- You are receiving this mail because: You are on the CC list for the bug.