-
-
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
New version is inconsistent with previously created VMs #4910
Comments
Have you tried removing and then opening it by clicking it? That did it for me. |
removing and opening it by finder will result in the following error. |
Can you provide your config.plist? |
In my case this was related to setting the CPU model to |
@ahamlinman Interesting. If you change it back to "host" from settings UI, does it still show up broken? |
@osy the option seems to be gone from the UI entirely. For reference, this is a 2021 M1 Max MacBook Pro running macOS 13.1. Here's my full |
Oh I see this makes sense. I think QEMU removed the option. I’ll have to work out a way to migrate the setting. |
Please do not close issues that have not been resolved, thanks! |
Changing CPU model to |
Yes but it’s not reasonable to expect everyone to know that. We need some way to detect and correct this issue. |
I am also getting this import unavailable error after update mac os to Sonoma, but I don't have a way to change CPU model to default in my case. the VM can't be launched and right-clicked, how should I able to change it? |
Describe the issue
After upgrading from 4.0.8 to 4.1.5 the existing VMs are greyed (unavailable) out with the error context of: this vm must be readded to utm from finder "location to VM"
however locating and opening it by finder will do nothing since nothing happens after you click the file.
** temporary and undesirable fixes**
downgrading to 4.0.8 will work but also I was able to boot a windows VM by extracting the qcow file from .utm file and creating a new vm in the latest utm version however I cant risk doing the same with my work VM since It has luks encryption and can break the boot configuration
Configuration
The text was updated successfully, but these errors were encountered: