http://bugzilla.suse.com/show_bug.cgi?id=989462 http://bugzilla.suse.com/show_bug.cgi?id=989462#c8 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber@suse.com --- Comment #8 from James Fehlig <jfehlig@suse.com> --- Heh, now I'm unsure about the proper way to invoke qemu with the aavmf images. For example on x86_64, with a guest using persistent UEFI variables, qemu is invoked as -drive file=/usr/share/qemu/ovmf-x86_64-ms-code.bin,if=pflash,format=raw,unit=0,readonly=on -drive file=/var/lib/libvirt/nvram/sles12sp2a2-ovfm-kvm_VARS.fd,if=pflash,format=raw,unit=1 On ARM, with a guest not using persistent variables, the linaro docs say to use -bios /path/to/code-image With persistent variables, the linaro docs recommend -pflash /path/to/code-image -pflash /path/to/var-image Gary, Alex, Andreas: Can you verify the correct qemu invocation for aavmf with and without persistent variables? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.