Black Screen when starting any VM in BigSur 11.1 ARM64

[elgambitero]

Describe the issue
The same symptoms as #2271, but in Apple Silicon. I did not find any other issue specific to M1 Macs.

Trying to boot any VM whatsoever, newly made or the ones that I had before results in a black screen, and nothing happens afterwards.

Configuration

• UTM Version: 2.0.19 (19)
• OS Version: BigSur 11.1
• Apple Silicon: Apple M1 8CPU/8GPU 16GB MacBook Pro 13"

Crash log
There is no crash

Debug log
Log is from a VM with Windows 10 ARM, configured as described in the tutorial. The symptoms are the same with any of the other VMs anyway.

For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.

Running:  -L /Applications/UTM.app/Contents/Resources/qemu -S -qmp tcp:127.0.0.1:4000,server,nowait -spice port=4001,addr=127.0.0.1,disable-ticketing,image-compression=off,playback-compression=off,streaming-video=off -machine virt,highmem=off -accel hvf -accel tcg,tb-size=2048 -bios /Applications/UTM.app/Contents/Resources/qemu/edk2-aarch64-code.fd -device virtio-ramfb -boot order=d -m 8192 -soundhw hda -name "Windows 10 ARM" -device qemu-xhci -device usb-tablet -device usb-mouse -device usb-kbd -device usb-storage,drive=drive0,removable=true -drive if=none,media=cdrom,id=drive0 -device nvme,drive=drive1,serial=drive1 -drive "if=none,media=disk,id=drive1,file=/Users/jaimegarciavillena/Library/Containers/com.utmapp.UTM/Data/Documents/Windows 10 ARM.utm/Images/Windows10_InsiderPreview_Client_ARM64_en-us_20231.VHDX,cache=writethrough" -device virtio-net-pci,netdev=net0 -netdev user,id=net0 -device virtio-serial -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,id=vdagent,debug=0,name=vdagent -uuid 56AE149A-F69F-4B3A-B6E9-53F6B089585E -rtc base=localtime
libqemu-aarch64-softmmu.utm.dylib: warning: '-soundhw hda' is deprecated, please use '-device intel-hda -device hda-duplex' instead

The log is extremely underwhelming anyway. I will be happy to provide any other log from any other test.

Upload VM

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ConfigurationVersion</key>
	<integer>2</integer>
	<key>Debug</key>
	<dict>
		<key>DebugLog</key>
		<true/>
	</dict>
	<key>Display</key>
	<dict>
		<key>ConsoleFont</key>
		<string>Menlo</string>
		<key>ConsoleFontSize</key>
		<integer>12</integer>
		<key>ConsoleOnly</key>
		<false/>
		<key>ConsoleTheme</key>
		<string>Default</string>
		<key>DisplayDownscaler</key>
		<string>linear</string>
		<key>DisplayUpscaler</key>
		<string>linear</string>
	</dict>
	<key>Drives</key>
	<array>
		<dict>
			<key>ImageType</key>
			<string>cd</string>
			<key>InterfaceType</key>
			<string>usb</string>
			<key>Removable</key>
			<true/>
		</dict>
		<dict>
			<key>ImagePath</key>
			<string>Windows10_InsiderPreview_Client_ARM64_en-us_20231.VHDX</string>
			<key>ImageType</key>
			<string>disk</string>
			<key>InterfaceType</key>
			<string>nvme</string>
		</dict>
	</array>
	<key>Info</key>
	<dict>
		<key>Icon</key>
		<string>windows</string>
		<key>IconCustom</key>
		<false/>
	</dict>
	<key>Input</key>
	<dict>
		<key>InputLegacy</key>
		<false/>
	</dict>
	<key>Networking</key>
	<dict>
		<key>NetworkCard</key>
		<string>virtio-net-pci</string>
		<key>NetworkEnabled</key>
		<true/>
	</dict>
	<key>Printing</key>
	<dict/>
	<key>Sharing</key>
	<dict>
		<key>ClipboardSharing</key>
		<true/>
	</dict>
	<key>Sound</key>
	<dict>
		<key>SoundCard</key>
		<string>hda</string>
		<key>SoundEnabled</key>
		<true/>
	</dict>
	<key>System</key>
	<dict>
		<key>Architecture</key>
		<string>aarch64</string>
		<key>BootDevice</key>
		<string>cd</string>
		<key>CPU</key>
		<string>cortex-a72</string>
		<key>JITCacheSize</key>
		<integer>0</integer>
		<key>MachineProperties</key>
		<string>highmem=off</string>
		<key>Memory</key>
		<integer>8192</integer>
		<key>SystemUUID</key>
		<string>56AE149A-F69F-4B3A-B6E9-53F6B089585E</string>
		<key>Target</key>
		<string>virt</string>
	</dict>
</dict>
</plist>

[osy]

I think this is related to #2286. Can you try v2.0.18 and let me know if it works for you?

[elgambitero]

I can confirm that v2.0.18 goes past the black screen, and boots the Windows installer. I'll try to stick with that while this gets fixed.

Is there any other test I can do for you guys?

[osy]

Closing as it will be fixed in v2.0.20.

[corwin-of-amber]

I am using v2.0.28 and I get a black screen with any display adapter other than virtio-ramfb. Is this expected as other devices are not supported in aarch64?

[osy]

Yes currently only virtio-ramfb is supported by QEMU.