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

Error Dialog When Starting a VM #3941

Closed
KinaKai opened this issue Apr 26, 2022 · 5 comments
Closed

Error Dialog When Starting a VM #3941

KinaKai opened this issue Apr 26, 2022 · 5 comments
Milestone

Comments

@KinaKai
Copy link

KinaKai commented Apr 26, 2022

Describe the issue
UTM throws an Error dialog without any additional context. When starting an existing ARM64 VM or a fresh ARM64 VM from the 3.2.0 version of UTM, a non-specific error dialog will appear. There's no other context in the UI, it's just a dialog with "Error".

Configuration

  • UTM Version: 3.2.0
  • OS Version: Fedora (but this is probably irrelevant)
  • Intel or Apple Silicon? Apple Silicon

Crash log
It appears that there's an RPC error in QEMU. Running UTM via the command-line yields the following output:

2022-04-25T19:46:51-0700 info com.utmapp.UTM : JIT: found entitlement
2022-04-25T19:47:00-0700 error com.utmapp.UTM : /Users/foo/Desktop/UTM.app/Contents/Frameworks/qemu-aarch64-softmmu.framework/Versions/A/qemu-aarch64-softmmu
2022-04-25 19:47:00.230 UTM[46318:1944847] Running:  -L /Users/foo/Desktop/UTM.app/Contents/Resources/qemu -S -qmp tcp:127.0.0.1:4000,server,nowait -nodefaults -vga none -spice "unix=on,addr=/Users/foo/Library/Group Containers/WDNLXAD4W8.com.utmapp.UTM/19C7C16A-DB29-46F4-B9B4-E334DB64F480.spice,disable-ticketing=on,image-compression=off,playback-compression=off,streaming-video=off,gl=on" -device virtio-ramfb-gl -cpu host -smp cpus=10,sockets=1,cores=10,threads=1 -machine virt,highmem=off -accel hvf -accel tcg,thread=multi,tb-size=1536 -drive if=pflash,format=raw,unit=0,file=/Users/foo/Desktop/UTM.app/Contents/Resources/qemu/edk2-aarch64-code.fd,readonly=on -drive if=pflash,unit=1,file=/Users/foo/Library/Containers/com.utmapp.UTM/Data/Documents/Fedora.utm/Images/efi_vars.fd -boot menu=on -m 6144 -device intel-hda -device hda-duplex -name Fedora -device nec-usb-xhci,id=usb-bus -device usb-tablet,bus=usb-bus.0 -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -device qemu-xhci,id=usb-controller-0 -chardev spicevmc,name=usbredir,id=usbredirchardev0 -device usb-redir,chardev=usbredirchardev0,id=usbredirdev0,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2,bus=usb-controller-0.0 -device usb-storage,drive=cdrom0,removable=true,bootindex=0,bus=usb-bus.0 -drive if=none,media=cdrom,id=cdrom0 -device virtio-blk-pci,drive=drive0,bootindex=1 -drive if=none,media=disk,id=drive0,file=/Users/foo/Library/Containers/com.utmapp.UTM/Data/Documents/Fedora.utm/Images/data.qcow2,discard=unmap,detect-zeroes=unmap -device virtio-net-pci,mac=16:3B:14:93:11:E7,netdev=net0 -netdev vmnet-shared,id=net0 -device virtio-serial -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,id=vdagent,debug=0,name=vdagent -uuid 19C7C16A-DB29-46F4-B9B4-E334DB64F480 -rtc base=localtime -device virtio-rng-pci
2022-04-25 19:47:00.234 UTM[46318:1944972] Stream error Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}
2022-04-25 19:47:00.234 UTM[46318:1944972] QMP stream error seen: Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}
2022-04-25 19:47:00.234 UTM[46318:1944972] QMP connection failed, retries left: 29
2022-04-25 19:47:01.335 UTM[46318:1944973] Stream error Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}
2022-04-25 19:47:01.335 UTM[46318:1944973] QMP stream error seen: Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}
2022-04-25 19:47:01.335 UTM[46318:1944973] Failed to connect to QMP: Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}
2022-04-25 19:47:01.341 UTM[46318:1944913] RPC: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}
2022-04-25 19:47:01.341 UTM[46318:1944913] error finding index: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}
2022-04-25 19:47:01.360 UTM[46318:1944847] RPC: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}
2022-04-25 19:47:01.360 UTM[46318:1944847] error finding index: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}
2022-04-25 19:47:07.260 UTM[46318:1944847] RPC: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}
2022-04-25 19:47:07.261 UTM[46318:1944847] error finding index: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}
2022-04-25 19:47:07.277 UTM[46318:1944974] RPC: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}
2022-04-25 19:47:07.277 UTM[46318:1944974] error finding index: Error Domain=com.utmapp.utm Code=-1 "No connection for RPC." UserInfo={NSLocalizedDescription=No connection for RPC.}

Debug log
N/A

Upload VM
N/A

@mkasu
Copy link

mkasu commented Apr 26, 2022

Can confirm same issue with a newly created ARM64 VM after updating to 3.2.0 (On M1 Max MacBook, macOS 12.3.1, Guest VM Windows 11)

@osy osy added this to the v3.2 milestone Apr 26, 2022
@osy osy closed this as completed in 1b1750e Apr 26, 2022
@osy
Copy link
Contributor

osy commented Apr 26, 2022

This will be fixed in the next release. For now a workaround is to add highmem=on to QEMU -> QEMU Machine Properties.

@3DCoded
Copy link

3DCoded commented May 1, 2022

I have the same issue with an Ubuntu Linux VM. When I add highmem=on it gives me the error h: no such file or directory

@jjphamm
Copy link

jjphamm commented Sep 29, 2022

I am using the latest UTM version 3.2.4. It seems to happen all the sudden. The work around is to download the UTM again and delete the older copy. The newly downloaded UTM just works and the VMs just work

@freemedom
Copy link

download the UTM again and delete the older copy

Specifically, how to do this? Thank you very much!

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

6 participants