-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot creat Linux VM: Could not open '/efi_vars.fd': No such file or directory #5419
Comments
Can you share your config.plist inside the .utm package? |
Well, there is no folder and no config.plist because the VM was never created. When I restart UTM, the VM in the sidebar is greyed out and clicking on it shows the following message: |
That’s really bizarre. Can you try v4.3.1 beta and see if that makes a difference? |
so do i host
guest
i tried UTM v4.3.1, it said next i did in my |
There's your problem. |
oh that's it. my linux virtual machine is created successfully. do you mean UTM doesn't support symbolic linked directory? |
UTM is an macOS sandboxed app. This is the case for every app that use Containers. @fegue does this apply to you as well? |
I have tried version 4.3.1 and it's failing even faster. |
You did not make any symlinks? |
No, I just used the app as intended (at least I think I did). |
Can you make sure |
The folder |
No, why don’t you try deleting the container and then open the app again? It should recreate the container |
Deleting Thank you so much for your great help and quick response! |
I will make sure Documents is created automatically in the future. |
Describe the issue
UTM always shows an error in a pop-up when trying to start the VM for the first time with the following message:
This happened with all Linux Distros I have tried so far:
I followed the instructions when creating a VM and didn't touch the defaults.
I tried both the .dmg and the App-Store version
Configuration
Crash log
No crash log exists
Debug log
The export Log button is greyed out
The text was updated successfully, but these errors were encountered: