utmctl list gives error: OSStatus error -1743

[wivaku]

Describe the issue
/Applications/UTM.app/Contents/MacOS/utmctl list does not list my VM and shows error instead:
Error from event: The operation couldn’t be completed. (OSStatus error -1743.)

Configuration

• UTM Version: 4.1.5 (74)
• macOS Version: 13.2
• Mac Chip (Intel, M1, ...): M2

Details
I have one running VM (Home Assistant).
The output:

$ /Applications/UTM.app/Contents/MacOS/utmctl list
Error from event: The operation couldn’t be completed. (OSStatus error -1743.)
UUID                                 Status   Name

[wivaku]

appears to have been a glitch. Is working now.

[junosuarez]

I ran into this issue as well - when I'm physically on my mac, using the builtin Terminal.app, utmctl list works after popping up a macos permissions dialog box. When I'm logged in via ssh from another machine, I consistently get Error from event: The operation couldn’t be completed. (OSStatus error -1743.).

Configuration

UTM Version: 4.1.5 (74)
macOS Version: 13.2.1
Mac Chip (Intel, M1, ...): M1

[flintlei]

@wivaku May I ask how did you resolve it? I got the same issue on UTM 4.1.6 (75) running on Mac mini M2.

[wivaku]

It is what @junosuarez described above.
When I log in through ssh and type the command I get the error message (error -1743).
When I am physically on my Mac I don't get the error message.

[osy]

Scripting bridge requires you to be logged in. You need to be able to launch a gui app

[flintlei]

@osy I got the error when I used VNC to access the Mac Mini. I am able to launch the GUI app. Is there other reason for the utmctl error?

Thanks

[logopk]

So actually the cli is almost useless if I try to manage machines remotely? Actually I am trying to run headless servers with utm and need to handle them via vpn/ssh.

[junosuarez]

My use case is similar to @logopk. Since I'm only running linux VMs, I switched to Multipass (another frontend for qemu) which works for my needs.

[max-wittig]

Same happens here with the latest beta version.

[ghost]

For me this error happens on my OCLP iMac15,1 running macOS 13.3.1 22E772610a. It happens regardless of whether I am logged in using SSH or physically typing this command in at the terminal. I tested on another Mac (MBP M1 Pro) and it worked totally fine there after showing a permissions dialog. For some reason, on my iMac the permissions dialog never shows (I cannot recall whether I might have accidentally dismissed it in the past, which could very well be why this is happening). It would be great if you can "reset" the permissions somehow.

[muzzah]

Going to chime in here and also complain :)

Im currently in Japan trying to manage some VMs located at home. I assumed this would work before I left and now discover that this does not work with the same error message. So now its useless. I think the fact that this does not work over ssh is a pretty big omission.

@wivaku Can you please reopen this issue. I feel like this should be fixed somehow.

[osy]

I think the new issue is fine, this one seemed to have a different root cause.