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

virtualization doesn't work after updating utm to the latest version #6861

Closed
michalzablocki319 opened this issue Dec 2, 2024 · 17 comments
Closed

Comments

@michalzablocki319
Copy link

I have a problem with windows virtualization in the latest version of utm. I have a mac with an apple m3 chip, and I am running macOS 15.2.
The last non beta version of utm worked fine for me, but after upgrading to the latest one, I can't run any virtual machines with windows.
The I cannot boot into windows for arm (I tried with windows 10 as well as 11, both new and existing virtual machines, even if I boot with an empty CD drive) I just get a blank screen and I can't do anything about that.
What's interesting is that I don't have this problem with emulating other architectures, it's just virtualization.

@osy
Copy link
Contributor

osy commented Dec 2, 2024

Can you provide a debug log as the issue template asked for?

@efroemling
Copy link

I might be running into the same thing. Just got the 4.6.2 update through the Mac App Store and now my Windows 11 arm VM just gives me a blank window when trying to start it. I created the VM a week or two ago using the recently released arm installer iso from Microsoft. I'm on an M4 Max MBP.

Debug log:
debug.log

Trying to create a fresh VM using the Microsoft installer iso seems to hang in the same way.

@markghayden
Copy link

My debian AMD64 VM won't startup after updating. I'm running on MacOS with M1 chip. QEMULauncher is stuck running at 300% CPU.

Sample of QEMULauncher.txt

@michalzablocki319
Copy link
Author

efroemling I have also updated by the mac app store if this might be of help.
Also, here is the debug log
debug.log

@jheinen
Copy link

jheinen commented Dec 2, 2024

Same for me, both with Debian 12 and Ubuntu 24.04.

@osy
Copy link
Contributor

osy commented Dec 2, 2024

Can someone provide a screenshot of this "blank screen"?

@osy osy pinned this issue Dec 2, 2024
@osy
Copy link
Contributor

osy commented Dec 2, 2024

I am able to reproduce it. Weirdly it's only an issue on the App Store build so I have no idea what's up.

@a15x
Copy link

a15x commented Dec 2, 2024

Yup, I’m having the same issue with the Mac App Store version. It runs smoothly with Apple’s Virtualization Framework, but I get a blank screen and high CPU usage (around 300%) if I virtualize (M3) with QEMU.

@osy osy closed this as completed in ff07e74 Dec 3, 2024
@markghayden
Copy link

I can confirm the problem seems to be with the app-store version (which is what I was using). When I download directly from web site, the problem does not occurs.

@osy
Copy link
Contributor

osy commented Dec 3, 2024

Yup, the problem has been addressed but Apple needs to approve the new update...

@markghayden
Copy link

Thanks! We'll try it out when the update is available.

@bitbemol
Copy link

bitbemol commented Dec 3, 2024

I'm experiencing a black screen with the text "Display output is not active" when trying to emulate or virtualize any OS.

I'm using macOS AppStore Version 4.6.2 (104) on Sequoia 15.1.1

I'll be waiting for the update on the AppStore for macOS mentioned before my post.

Thanks a lot for the hard work, I hope the update also fixes my issue.

Screenshot 2024-12-03 at 6 04 02 AM

@osy
Copy link
Contributor

osy commented Dec 3, 2024

In the meantime, I've found a workaround:

  1. Quit UTM if it is currently open
  2. Open Finder and navigate to Applications
  3. Right click UTM and choose Compress "UTM"
  4. Delete UTM from Applications
  5. Double click UTM.zip to unzip and restore UTM
  6. Delete UTM.zip and you can now re-launch UTM

@osy
Copy link
Contributor

osy commented Dec 4, 2024

Heads up v4.6.3 is now out on the App Store. Please manually update it if you didn't automatically get the update.

@michalzablocki319
Copy link
Author

@osy Thanks. It works fine now. But what exactly did you do to fix the issue. Apparently it was only mac app store issue.

@bitbemol
Copy link

bitbemol commented Dec 4, 2024

@osy thanks a lot !, tried with some emulated ubuntu and the display now outputs correctly. I also like to know what was the fix since only the App Store version was affected?

@osy
Copy link
Contributor

osy commented Dec 4, 2024

I have no idea what the issue was and it was a huge pain to debug because you can't attach the debugger to App Store apps. But the issue was that the BIOS was being read as 0 size and it only affected the App Store version because of something weird with how macOS installs app store apps. I'm guessing it had something to do with the fact that the BIOS was read-only inside the app bundle so I just copied all the BIOS to a read-writable location and it works now but I don't know why.

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

7 participants