osy
osy
I think this may be a driver issue on your hackintosh. Can you test on a real mac?
If you add a new "drive" and set the type to "Kernel" it will create that parameter. https://docs.getutm.app/settings-qemu/drive/drive/#image-type
Have you tried https://docs.getutm.app/scripting/cheat-sheet/
We don't expose arguments because UTM doesn't just call QEMU. It uses a fork of QEMU and is integrated with UTM's backend. For example we don't support VNC at all.
Oh you're right, I guess I forgot about that
How are you calling utmctl?
Can you run `ls -l $(which utmctl)` and paste the output?
I've been playing around with this and it seems like it's actually not possible for a sandboxed CLI app to know what's its own real path is. ```swift /// Find...
It is indeed distributed on MAS. And also because of the added security (if there's a QEMU bug, it won't automatically be able to rw your entire drive).
What architecture are you using? PC Speaker (as the name implies) only works for PCs (x86_64/i386)