Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 698878 - app-emulation/qemu-4.1.0 - Unable to complete install: 'operation failed: unable to find any master var store for loader: /usr/share/qemu/edk2-x86_64-code.fd'
Summary: app-emulation/qemu-4.1.0 - Unable to complete install: 'operation failed: una...
Status: RESOLVED DUPLICATE of bug 698890
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Matthias Maier
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-29 19:19 UTC by Anton Gubarkov
Modified: 2020-02-06 21:31 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Gubarkov 2019-10-29 19:19:46 UTC
PF16W6Y2 /etc/libvirt # ls -l /usr/share/qemu/
total 223150
-rw-r--r-- 1 root root     3211 сен 23 13:10 bamboo.dtb
lrwxrwxrwx 1 root root       24 сен 23 13:10 bios-256k.bin -> ../seabios/bios-256k.bin
lrwxrwxrwx 1 root root       19 сен 23 13:10 bios.bin -> ../seabios/bios.bin
-rw-r--r-- 1 root root     9779 сен 23 13:10 canyonlands.dtb
-rw-r--r-- 1 root root 67108864 сен 23 13:10 edk2-aarch64-code.fd
-rw-r--r-- 1 root root 67108864 сен 23 13:10 edk2-arm-code.fd
-rw-r--r-- 1 root root 67108864 сен 23 13:10 edk2-arm-vars.fd
-rw-r--r-- 1 root root  3653632 сен 23 13:10 edk2-i386-code.fd
-rw-r--r-- 1 root root  3653632 сен 23 13:10 edk2-i386-secure-code.fd
-rw-r--r-- 1 root root   540672 сен 23 13:10 edk2-i386-vars.fd
-rw-r--r-- 1 root root    42903 сен 23 13:10 edk2-licenses.txt
-rw-r--r-- 1 root root  3653632 сен 23 13:10 edk2-x86_64-code.fd
-rw-r--r-- 1 root root  3653632 сен 23 13:10 edk2-x86_64-secure-code.fd
-rw-r--r-- 1 root root   240128 сен 23 13:10 efi-e1000e.rom
-rw-r--r-- 1 root root   240128 сен 23 13:10 efi-e1000.rom
-rw-r--r-- 1 root root   240128 сен 23 13:10 efi-eepro100.rom
-rw-r--r-- 1 root root   238592 сен 23 13:10 efi-ne2k_pci.rom
-rw-r--r-- 1 root root   238592 сен 23 13:10 efi-pcnet.rom
-rw-r--r-- 1 root root   242688 сен 23 13:10 efi-rtl8139.rom
-rw-r--r-- 1 root root   242688 сен 23 13:10 efi-virtio.rom
-rw-r--r-- 1 root root   236032 сен 23 13:10 efi-vmxnet3.rom
drwxr-xr-x 2 root root        8 сен 23 13:10 firmware
-rw-r--r-- 1 root root   783724 сен 23 13:10 hppa-firmware.img
drwxr-xr-x 2 root root       36 сен 23 13:10 keymaps
-rw-r--r-- 1 root root     9216 сен 23 13:10 kvmvapic.bin
-rw-r--r-- 1 root root     1024 сен 23 13:10 linuxboot.bin
-rw-r--r-- 1 root root     1536 сен 23 13:10 linuxboot_dma.bin
-rw-r--r-- 1 root root     1024 сен 23 13:10 multiboot.bin
-rw-r--r-- 1 root root   767256 сен 23 13:10 openbios-ppc
-rw-r--r-- 1 root root   382048 сен 23 13:10 openbios-sparc32
-rw-r--r-- 1 root root  1593408 сен 23 13:10 openbios-sparc64
-rw-r--r-- 1 root root    36888 сен 23 13:10 opensbi-riscv32-virt-fw_jump.bin
-rw-r--r-- 1 root root    40968 сен 23 13:10 opensbi-riscv64-sifive_u-fw_jump.bin
-rw-r--r-- 1 root root    40968 сен 23 13:10 opensbi-riscv64-virt-fw_jump.bin
-rw-r--r-- 1 root root   156328 сен 23 13:10 palcode-clipper
-rw-r--r-- 1 root root     9982 сен 23 13:10 petalogix-ml605.dtb
-rw-r--r-- 1 root root     8259 сен 23 13:10 petalogix-s3adsp1800.dtb
-rw-r--r-- 1 root root  1048576 сен 23 13:10 ppc_rom.bin
-rw-r--r-- 1 root root     1536 сен 23 13:10 pvh.bin
lrwxrwxrwx 1 root root       20 сен 23 13:10 pxe-e1000.rom -> ../ipxe/8086100e.rom
lrwxrwxrwx 1 root root       20 сен 23 13:10 pxe-eepro100.rom -> ../ipxe/80861209.rom
lrwxrwxrwx 1 root root       20 сен 23 13:10 pxe-ne2k_pci.rom -> ../ipxe/10500940.rom
lrwxrwxrwx 1 root root       20 сен 23 13:10 pxe-pcnet.rom -> ../ipxe/10222000.rom
lrwxrwxrwx 1 root root       20 сен 23 13:10 pxe-rtl8139.rom -> ../ipxe/10ec8139.rom
lrwxrwxrwx 1 root root       20 сен 23 13:10 pxe-virtio.rom -> ../ipxe/1af41000.rom
-rw-r--r-- 1 root root      850 сен 23 13:10 QEMU,cgthree.bin
-rw-r--r-- 1 root root   154542 сен 23 13:10 qemu-nsis.bmp
-rw-r--r-- 1 root root     1402 сен 23 13:10 QEMU,tcx.bin
-rw-r--r-- 1 root root    18752 сен 23 13:10 qemu_vga.ndrv
-rw-r--r-- 1 root root    42608 сен 23 13:10 s390-ccw.img
-rw-r--r-- 1 root root    67232 сен 23 13:10 s390-netboot.img
lrwxrwxrwx 1 root root       22 сен 23 13:10 sgabios.bin -> ../sgabios/sgabios.bin
-rw-r--r-- 1 root root  1591384 сен 23 13:10 skiboot.lid
-rw-r--r-- 1 root root   926432 сен 23 13:10 slof.bin
-rw-r--r-- 1 root root       20 сен 23 13:10 spapr-rtas.bin
-rw-r--r-- 1 root root    67941 сен 23 13:10 trace-events-all
-rw-r--r-- 1 root root   349148 сен 23 13:10 u-boot.e500
-rw-r--r-- 1 root root   524288 сен 23 13:10 u-boot-sam460-20100605.bin
-rw-r--r-- 1 root root    38912 сен 23 13:10 vgabios-ati.bin
lrwxrwxrwx 1 root root       32 сен 23 13:10 vgabios.bin -> ../seavgabios/vgabios-isavga.bin
-rw-r--r-- 1 root root    27648 сен 23 13:10 vgabios-bochs-display.bin
lrwxrwxrwx 1 root root       32 сен 23 13:10 vgabios-cirrus.bin -> ../seavgabios/vgabios-cirrus.bin
lrwxrwxrwx 1 root root       29 сен 23 13:10 vgabios-qxl.bin -> ../seavgabios/vgabios-qxl.bin
-rw-r--r-- 1 root root    28160 сен 23 13:10 vgabios-ramfb.bin
lrwxrwxrwx 1 root root       32 сен 23 13:10 vgabios-stdvga.bin -> ../seavgabios/vgabios-stdvga.bin
lrwxrwxrwx 1 root root       32 сен 23 13:10 vgabios-virtio.bin -> ../seavgabios/vgabios-virtio.bin
lrwxrwxrwx 1 root root       32 сен 23 13:10 vgabios-vmware.bin -> ../seavgabios/vgabios-vmware.bin
drwxr-xr-x 2 root root        3 сен 23 13:10 vhost-user
Comment 1 Anton Gubarkov 2019-10-29 19:22:07 UTC
As the result, I'm unable to create the new x86_64 UEFI VM using libvrt's virt-manager. 

The virt-manager is now hardcoded to use internal qemu shipped UEFI and vars images. The usual trick with setting nvram list in qemu.conf no longer works. Should I raise a separate bug for app-emulation/libvirt-5.8.0?
Comment 2 Anton Gubarkov 2019-10-29 19:23:38 UTC
For the sake of completeness:

when I start newly created VM I get 
Unable to complete install: 'operation failed: unable to find any master var store for loader: /usr/share/qemu/edk2-x86_64-code.fd'
Comment 3 Nikolay Kichukov 2019-11-08 17:06:24 UTC
Any known workaround for this at this stage?
Comment 4 Nikolay Kichukov 2019-11-08 17:15:38 UTC
In my case this is failing for aarch64:

unable to find any master var store for loader: /usr/share/qemu/edk2-aarch64-code.fd'
Comment 5 brent 2019-11-14 11:14:14 UTC
(In reply to Nikolay Kichukov from comment #3)
> Any known workaround for this at this stage?

I've found one, but fair warning: it's a PITA.

I'm assuming you're using virt-manager to create, yes? If so, you can thankfully edit the raw XML for libvirt.

First, make sure it's enabled. In virt-manager:

 Edit > Preferences > General
- Ensure that "Enable XML editing" is checked

Close, and create a guest as normal. When it gets to the final stage/screen ("Step 5 of 5"), *ensure* that you check "Customize configuration before install", then click the "Finish" button.

It then takes you to the new VM customization screen. NORMALLY you'd just be able to select your UEFI image in the dropdown, but it no longer recognizes them in the conf. So instead, click the "XML" tab under "Overview".

You'll probably see something like this:


  <os>
    <type arch="x86_64" machine="q35">hvm</type>
    <boot dev="hd"/>
  </os>


Change that to:


  <os>
    <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type>
    <loader readonly='yes' type='pflash'>/PATH/TO/OVMF_CODE.fd</loader>
    <nvram>/PATH/TO/NVRAM/VARS/VMNAME_VARS.fd</nvram>
  </os>


obviously replacing /PATH/TO/OVMF_CODE.fd with the actual path to your OVMF loader, /PATH/TO/NVRAM/VARS with the directory to your NVRAM vars, and VMNAME with the respective vm name. The path and filename for nvram isn't *quite* as important (and doesn't- and shouldn't- pre-exist), as long as libvirtd has write access to the directory to create the vars.

Then click the "Apply" button and then *directly* click the "Begin Installation" button. Clicking around in other places *shouldn't* overwrite the override you just manually made (it didn't in my *very* cursory testing), but why risk it?

It *should* boot just fine via OVMF for UEFI. I tested this on an Arch host (qemu 4.1.0, libvirt 5.8.0, virt-manager 2.2.1), but I can't think of why it'd be any different for you Gentoo guys (I used to be one! The version parity between the two is *really* close so this workaround should work).
Comment 6 Louis Frayser 2020-02-05 16:43:06 UTC
Just want to *confirm* 

The current status is still "UNCONFIRMED" and I'm also having this problem.

app-emulation/libvirt-5.10.0
app-emulation/qemu-4.2.0-r1
Comment 7 Matthias Maier gentoo-dev 2020-02-06 21:31:17 UTC

*** This bug has been marked as a duplicate of bug 698890 ***