Skip to content
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

Closed
amirseyedian opened this issue Jan 6, 2023 · 12 comments
Closed

New version is inconsistent with previously created VMs #4910

amirseyedian opened this issue Jan 6, 2023 · 12 comments
Milestone

Comments

@amirseyedian
Copy link

Describe the issue
Screen Shot 2023-01-06 at 15 13 47

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

  • UTM Version: 4.1.5
  • macOS Version: 12.3.1
  • Mac Chip (Intel, M1, ...):m1 MBA 2020
@Terabyte1385
Copy link

Have you tried removing and then opening it by clicking it? That did it for me.

@amirseyedian
Copy link
Author

removing and opening it by finder will result in the following error.
Cannot import this VM. Either the configuration is invalid, created in a newer version of UTM, or on a platform that is incompatible with this version of UTM.

@osy
Copy link
Contributor

osy commented Jan 6, 2023

Can you provide your config.plist?

@amirseyedian
Copy link
Author

amirseyedian commented Jan 6, 2023

@osy osy added this to the v4.2 milestone Jan 6, 2023
@ahamlinman
Copy link

In my case this was related to setting the CPU model to host, and the linked plist shows the same configuration. Hand-editing the plist to change host to default resolved the issue for me.

@osy
Copy link
Contributor

osy commented Jan 8, 2023

@ahamlinman Interesting. If you change it back to "host" from settings UI, does it still show up broken?

@ahamlinman
Copy link

ahamlinman commented Jan 9, 2023

@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 config.plist.

Screenshot of UTM 4.1.5 displaying the CPU options dropdown in the settings UI

@osy
Copy link
Contributor

osy commented Jan 9, 2023

Oh I see this makes sense. I think QEMU removed the option. I’ll have to work out a way to migrate the setting.

@osy osy reopened this Jan 12, 2023
@osy
Copy link
Contributor

osy commented Jan 12, 2023

Please do not close issues that have not been resolved, thanks!

@amirseyedian
Copy link
Author

Changing CPU model to default fixes the problem

@osy
Copy link
Contributor

osy commented Jan 12, 2023

Yes but it’s not reasonable to expect everyone to know that. We need some way to detect and correct this issue.

@osy osy closed this as completed in d1d2899 Mar 3, 2023
@Aiqin-Aiven
Copy link

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?
my config.plist file: https://github.com/Aiqin-Aiven/misc/blob/master/config.plist.backup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants