unable to find any master var store for loader

[galtline]

I can still launch from Basic.SH but I am not able to load from Virtual Machine. I followed the directions here:

https://passthroughpo.st/new-and-improved-mac-os-tutorial-part-1-the-basics/#disqus_thread

When I start the Virtual machine from VMM.

Error starting domain: operation failed: unable to find any master var store for loader: /Documents/macOS-Simple-KVM/firmware/OVMF_CODE.fd

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1234, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: operation failed: unable to find any master var store for loader: /Documents/macOS-Simple-KVM/firmware/OVMF_CODE.fd

[mike-lloyd03]

I was having the same problem but I figured it out. For some reason, git cloning the repo does not include OVMF_VARS-1024x768.fd. Downloading the file and moving it into the firmware directory fixed the problem.

[Sepehr13]

i'm having the same problem and the file "OVMF_VARS-1024x768.fd" exists but the error is still there

`Error starting domain: operation failed: unable to find any master var store for loader: "/media/sepehr/Local Disk/MacKVM/macOS-Simple-KVM/firmware/OVMF_CODE.fd"

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1234, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: operation failed: unable to find any master var store for loader: "/media/sepehr/Local Disk/MacKVM/macOS-Simple-KVM/firmware/OVMF_CODE.fd"`

[richterlevania3]

Had this same problem. Manjaro Linux on a Ryzen 3600X. One entire SSD for it. At this point I will just leave it.

[HaleTom]

My error message specified $HOME/OSX-KVM/OVMF_CODE.fd which didn't exist because I didn't git clone under $HOME. I moved symlinked to the correct directory and the error went away.

Is there any way of setting the expected directory?

[BongSolo]

My error message specified $HOME/OSX-KVM/OVMF_CODE.fd which didn't exist because I didn't git clone under $HOME. I moved symlinked to the correct directory and the error went away.

Is there any way of setting the expected directory?

i had same issue i ended up editing the xml file finding all the entries with $HOME/OSX-KVM/ with whatever dir my files are in. Hope this makes sense.

[ghost]

On Mint 20.1:
Error starting domain: operation failed: unable to find any master var store for loader: /home/frederic/macOS-Simple-KVM/firmware/OVMF_CODE.fd

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup

[OmkoBass]

You might be able to fix this by using
sudo ./make.sh --add
instead of
./make.sh --add

[ghost]

Thank you very much! Le mer. 26 janv. 2022 à 14:27, Omer ***@***.***> a écrit :

…

You might be able to fix this by using sudo ./make.sh --add instead of ./make.sh --add — Reply to this email directly, view it on GitHub <#395 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AROETRGUBLAZFCCGZWLJEN3UX7ZDJANCNFSM4VSI7MHA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[cilahn]

First foxlet thank you for your hard work going into this. Second, i could trigger this bug when using virt-manager. If you delete the virtual machine added via sudo ./make --add the and allow virt-manager to delete all files the 'OVMF_VARS-1024x768.fd' gets deleted too - even it's not listed for deletion.
Hope it helps a bit.

[notAperson535]

@cilahn I wouldn't let virt-manager delete the files

[fredericodevbtw]

This fixed the error for me, thanks @cilahn!