-
-
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
MacBook Pro M4: QEMU error: QEMU exited from an error: With SME enabled, at least one vector length must be enabled. #6790
Comments
Experiencing this as well. |
Hello, I have the same problem. it seems to be an issue with the M4's new scalable matrix extension. I have the same beta as you, hopefully it gets fixed soon. |
This is a bug in QEMU https://gitlab.com/qemu-project/qemu/-/issues/2665 but we will add a workaround in the next release. |
Any idea on when the next release will take place? Thank you. |
I'm also experiencing this on my M4 Mac mini. Hope to see a fix soon. Thanks! |
Same issue here following public macOS 15.2 release. Where's the fix? |
Please disregard. My UTM app was out of date. Resolved with the latest release. Thanks, team! |
Would you be possible to submit this patch to the upstream? Context: |
@AkihiroSuda No, because as the patch states "DO NOT MERGE" because it is not a proper fix. We (UTM) do not use SME so it does not matter. Upstream needs to handle more than Apple Mx processors. Please follow https://gitlab.com/qemu-project/qemu/-/issues/2665 for a proper fix. |
so may I know how to fix this issue? all of my VM are not be able to started after I upgraded the MacOS patches :( |
Update to the latest UTM |
Oh, there is a new version! Thank you so much! |
Describe the issue
QEMU error: QEMU exited from an error: With SME enabled, at least one vector length must be enabled.
The VM was working before on a M1 MacBook Pro and transferred to an M4 MacBook Pro using Apples System migration tool.
Configuration
Debug log
QEMU-debug.log
Upload VM
config.plist.zip
The text was updated successfully, but these errors were encountered: