Closed Oyetomi closed 3 years ago
@conath , @osy please can you help me out ?, i downloaded a new iso file, did a qemu-img check -r all Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX says file is okay but i still keep getting a connection refused error
Hi @virginsince1997 to help investigate the source of the issue, could you please try to re-download UTM, then copy it to /Applications. Finally, right click (two finger tap on Trackpad) on UTM.app and select "Open". This should enable you to use UTM normally. Please let me know if this works for you. Thanks!
A similar (possibly identical) issue has been reported via Discord. "Brent" has provided a crash log that is generated along with the error message.
Notably, the crash EXC_BAD_ACCESS (SIGSEGV)
happens in Dispatch queue: com.utmapp.UTM.JSONStream
.
Thread 12 Crashed:: Dispatch queue: com.utmapp.UTM.JSONStream
0 libobjc.A.dylib 0x00000001a540f178 objc_msgSend + 24
1 com.utmapp.UTM 0x00000001047b88dc 0x10477c000 + 248028
2 com.apple.CoreFoundation 0x00000001a569c894 _signalEventSync + 216
3 com.apple.CoreFoundation 0x00000001a56eeb20 ___signalEventQueue_block_invoke + 28
4 libdispatch.dylib 0x00000001a53c78bc _dispatch_call_block_and_release + 32
5 libdispatch.dylib 0x00000001a53c9420 _dispatch_client_callout + 20
6 libdispatch.dylib 0x00000001a53d077c _dispatch_lane_serial_drain + 580
7 libdispatch.dylib 0x00000001a53d12cc _dispatch_lane_invoke + 408
8 libdispatch.dylib 0x00000001a53db3fc _dispatch_workloop_worker_thread + 708
9 libsystem_pthread.dylib 0x00000001a5572060 _pthread_wqthread + 276
10 libsystem_pthread.dylib 0x00000001a5570d94 start_wqthread + 8
@conath thank you for your response, I've tried what you recommend but still not working, sometimes it crashes, and sometimes I get the connection error. I also tried joining the discord but the links are expired, could you please share?
@conath the crash is identical to mine
@virginsince1997 any reason in particular why you're not on a more recent version of macOS? Your crash log reads "11.1", latest is "11.5.2".
I noticed this in Brent's log as well, he's on 11.2.2.
There is an interesting error in the debug log as well:
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
@conath thank you for your time, I'd try to update and see how it goes
@virginsince1997 any reason in particular why you're not on a more recent version of macOS? Your crash log reads "11.1", latest is "11.5.2".
I noticed this in Brent's log as well, he's on 11.2.2.
There is an interesting error in the debug log as well:
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec(). Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
@conath i updated to the latest macos but still got this error
@conath thank you very much for your time , i really appreciate it , its working now. i updated the OS as you suggested , and i also changed network to bridged in utm settings.
Nice, enjoy!
this is my first time starting the vm, i converted the windows10 iso to qcow2 , imported the spicetools iso, started the VM and got this error
"
The operation couldn’t be completed. Connection refused"
Configuration
Debug log debug.log