Disable suspend/resume when no compatible disk image is loaded

[BenjyWiener]

If UTM is exited while a VM is suspended, attempting to resume the VM after restarting UTM results in the following message:

QEMU exited from an error: qemu: info: Spice:
reds.c:3334:spice_server_remove_interface: remove
SPICE_INTERFACE_RECORD

After pressing "OK" UTM exits, and then the VM can be restarted normally.

To Reproduce

1. Start a VM (this has happened for every VM I've tried, including TinyCore)
2. Suspend the VM
3. Exit UTM using the 'X' (alternatively, leave UTM in the background until iOS kills it)
4. Relaunch UTM and attempt to resume the VM

Xcode debug output (from second run, trying to resume VM)
Xcode debug.log

Debug log
debug.log

Upload VM
TinyCore.utm.zip

[osy]

Did you change any settings?

[BenjyWiener]

No, these results are all from a fresh installation in the Simulator (but I get the same results on my device).

[osy]

qemu: No block device supports snapshots

So the issue is that you don't have a HDD image. That's needed for suspend/resume. I will make this more clear in a future release.

[BenjyWiener]

What are the HDD requirements? On my VMs that do have an HDD image, I get the following line in the debug output:

qemu: Device ‘drive0’ is writable but does not support snapshots

The image is a raw disk image (created with UTM) mounted as a disk image on ide.

[osy]

It needs to be qcow2

[BenjyWiener]

Does UTM only create raw images, or does it go based on the provided file extension?

[osy]

The creation supports two types. If you check the box it’s qcow2 otherwise it’s raw.

[BenjyWiener]

Got it. This should probably be made more clear in the app. Especially since the placeholder text is “hda.img” (and raw images can be sparse). Should I open a new issue?

[osy]

No need, I’ll use this issue to improve it.