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

Created attachment 870374 [details] VMI startup log

Base on the above log, looks that the VM used OVMF_CODE.secboot.fd and OVMF_VARS.secboot.fd as EFI firmware: {"component":"virt-launcher","level":"info","msg":"\t\t<loader readonly=\"yes\" secure=\"yes\" type=\"pflash\">/usr/share/OVMF/OVMF_CODE.secboot.fd</loader>","subcomponent":"libvirt","timestamp":"2023-10-19T17:30:50.321164Z"} {"component":"virt-launcher","level":"info","msg":"\t\t<nvram template=\"/usr/share/OVMF/OVMF_VARS.secboot.fd\">/tmp/default_testvmi</nvram>","subcomponent":"libvirt","timestamp":"2023-10-19T17:30:50.321177Z"} But those files are not from qemu-ovmf-x86_64 RPM. Hi Vasily, Do you know where are OVMF_CODE.secboot.fd and OVMF_VARS.secboot.fd from? -- You are receiving this mail because: You are on the CC list for the bug.