4.3.4: Blank screen or "Guest has not initialized the display (yet)." on start

[fabiensanglard]

Describe the issue
I am unable to install Windows 11. After following instructions found here https://docs.getutm.app/guides/windows/, I run the VM and the screen remains blank.

Configuration

• UTM Version: Version 4.3.4 (86)
• macOS Version: Ventura 13.5
• Mac Chip: M1

Crash log
UTM does not crash.

Debug log
debug.log

Upload VM
config.plist.zip

Screenshot of blank:

[fabiensanglard]

Note that I tried to use both Windows11_InsiderPreview_Client_ARM64_en-us_23506.VHDX or 22621.1_MULTI_ARM64_EN-US.ISO and got the same result each time.

[erayd]

I am experiencing the same no-display issue when attempting to boot an existing Win11 (virtio-ramfb-gl) and Gentoo (virtio-gpu-pci) following the update of UTM to v4.3.4 - so this may not be just a new-VM problem. Host is a M1 running Ventura 13.4.1(c).

[maederm]

Experiencing the same issue as well with a newly created Windows VM using the default settings from the wizard. Existing VMs also doesn't work. (Doesn't matter if ARM or Standard PC). Don't see anything useful in debug logs.

[osy]

Does restarting your computer help?

[osy]

Also can you try adding a serial port to the VM and starting it and see if anything shows up in the terminal? There may be an error message there.

[maederm]

Does restarting your computer help?

Unfortuantely no.

[maederm]

Also can you try adding a serial port to the VM and starting it and see if anything shows up in the terminal? There may be an error message there.

There isn't any output on the serial console as well.

Btw., I use the AppStore Version of UTM 4.3.4 (86)

[osy]

This is a bizarre bug. I can only reproduce it on App Store/TestFlight builds but not on the GitHub DMG or development builds...

[Jimiwho]

I have the same issue since the update to Version 4.3.4 (86) from the App Store. MacOS Ventura 13.5 (Apple M1)

[alybally04]

I also just updated to 4.3.4 on the App Store (Ventura 13.5) and have the same issue with all of my existing Windows 11 and Ubuntu VMs (but not Windows XP for some reason).

The VM uses approx 40% of CPU while displaying "Guest has not initialized the display (yet)." indefinitely and never boots.

All of the VMs were working perfectly before updating.

[nickdowell]

I'm also affected, as reported in #5525 (duplicate)

[florianschendel]

I have the same problem. App was installed via Apple App Store. Version 4.3.4 (86)

[yevmel]

as others mentioned in similar posts, only UTM from app store is affected. My workaround at the moment is using UTM from the website: https://mac.getutm.app

[the-man-machine]

Same, latest AppStore version, Linux arm64 VM, whether existing or trying to set up a new one — "guest has not initialized the display" and 300% CPU usage.

[osy]

The issue with the Mac App Store build has been identified as QEMU reading the UEFI BIOS as all 00s while the DMG build reads it properly. This is extremely weird because we use the exact same binary for both with the same entitlements. The only difference is the code signature. My hunch is that there is some weird race condition in QEMU when trying to read the UEFI BIOS and so the current thinking is to downgrade to QEMU 7.2.0. I am trying to build it right now and test it and if it works, I'll submit an update to the MAS ASAP to get this resolved. This is super frustrating because I could have never imagined that the MAS build would act differently and I am still trying to figure out exactly why. As it currently stands every VM that uses UEFI will not boot so this is a pretty big issue and I apologize for not catching it earlier.

[fabiensanglard]

The irony of the timing. Having used UTM for a while, I decided yesterday to buy it via the AppStore...only to find out it was broken :P ! Thank you for all your hard work, UTM rules.

[osy]

v4.3.5 has been tested and should resolve the issue by downgrading QEMU to v7.2.0 and EDK2 to edk2-stable202102. As soon as Apple approves it, the update should go out to App Store users. Then once the cause of the issue is figured out, we'll release another update.

Update: It's been approved, if you don't see the update, manually open App Store and refresh the updates tab.

[yevmel]

@osy thank you very much 👍

i already migrated my VMs yesterday to version of UTM i downloaded from https://mac.getutm.app/ and removed the one i downloaded from the App Store. Is there any benefit using the version from App Store beside getting notified about new versions of the app?

[deciphr102]

Any luck with this? i am facing similar issue, 3 weeks back opened and issue but dont see any recommendation or solution on that.

#5479

[ClausHansn]

i switched to version 3.15 and install ubuntu (it was the one i had no screen on) then upgraded to the latest version and all work now win11 macos 14 and 9 :)

mac m1

[deciphr102]

i switched to version 3.15 and install ubuntu (it was the one i had no screen on) then upgraded to the latest version and all work now win11 macos 14 and 9 :)

mac m1

Are you using dual screen in your machine

[ClausHansn]

no just 1
it was only when I had to reinstall ubuntu the others have worked all the time 4.3.4 and 4.3.5

[hrpomrx]

FWIW I have that message if I try to boot a Win 11 guest (MBA 15 M2 host) with a projector connected. I'm on UTM 4.3.5.

Without the projector connected to the MBA, Win 11 boots fine but, when I subsequently plug in the projector the screen in the guest window goes blank (white).

Hopefully this 4.4.0 version is officially released soon. Thanks.

[Michi-Graf]

Im having the same problem with UTM on my M1 Mac with UTM 4.3.5 trying to run Linux with QEMU.
I tried different versions of QEMU (7.2, 7.1, .. a few), but am still getting the "Guest has not initialized the display (yet).

Any news or suggestions?
I possible, I'd like to keep the App Store version because of the automatic updates...

[hrpomrx]

Tried 4.4.3 beta dmg but still getting the "Guest has not initialized the display (yet)". M2 MBA, Win 11 Guest.

Update: I managed to get rid of the message and boot fine, after playing around with the display settings.

[Bonnie39]

@hrpomrx What display settings ended up working? I'm getting the same issue too

[hrpomrx]

@hrpomrx What display settings ended up working? I'm getting the same issue too

Hi, @Bonnie39.

At some point I had used another display like VGA and had set the VGA Device RAM to something other than the (grayed out) default which, in my case was 16. I had set it higher than that and saved. On switching back to virtio-ramfb, I got the error....until I switched back to VGA, deleted my custom VGA Device RAM setting, saved, and went back to virtio-ramfb. Then it magically worked. YMMV, but I think there's maybe a rogue ram variable floating around somewhere. I'd suggest going to other display types and removing any custom RAM settings you might have.

[noahwo]

For me, I had the similar issue and could not solve with the solutions mentioned in this Issue page. I actually found that was due to an option checked without I fully understanding it.

The option "Boot from kernel image" in the page when setting up should be unchecked. Then I entered the VM successfully.

[joekrump]

@hrpomrx What display settings ended up working? I'm getting the same issue too

Hi, @Bonnie39.

At some point I had used another display like VGA and had set the VGA Device RAM to something other than the (grayed out) default which, in my case was 16. I had set it higher than that and saved. On switching back to virtio-ramfb, I got the error....until I switched back to VGA, deleted my custom VGA Device RAM setting, saved, and went back to virtio-ramfb. Then it magically worked. YMMV, but I think there's maybe a rogue ram variable floating around somewhere. I'd suggest going to other display types and removing any custom RAM settings you might have.

thanks @hrpomrx . This worked for me:

1. Set to VGA and custom VGA device ram:

2. Saved this setting
3. Opened settings again. Set display hardward as virtio-ramfb
4. Saved this setting
5. Opened up the VM and it worked!

[serifcetin]

My resolution was simple. I clicked the shut down button on the black window and turned on again. And it worked. I wasn't expecting that. :)

[roya9762]

I'm facing same issue, tried all action which posted above still facing same issue. Guest has not initialised the display yet. Can any suggest the remedy ? How to get rid of this issue ?

I'm using latest version of UTM on M2 MAC

[salmantec]

Hey, I tried this and it worked for me

#5525 (comment)

[FoxLy1312]

Same problem here im running iPhone 15
Latest IOS UTM from appstore