serbert

My virtual disks have the suffix `img`. Creating a snapshot fails with: ``` WARNING: Image format was not specified for '95E3BDD3-62C7-4CA3-8FE1-BC046EBFC26A.img' and probing guessed raw. Automatically detecting the format is...

Hm, after converting to `qcow2` UTM doesn't find the image anymore. When I import the image file manually, then UTM tries to start the image but the window stays black....

`$ qemu-img convert -f raw -O qcow2 95E3BDD3-62C7-4CA3-8FE1-BC046EBFC26A.img 95E3BDD3-62C7-4CA3-8FE1-BC046EBFC26A.qcow2` ``` $ qemu-img info 95E3BDD3-62C7-4CA3-8FE1-BC046EBFC26A.img image: 95E3BDD3-62C7-4CA3-8FE1-BC046EBFC26A.img file format: raw virtual size: 64 GiB (68719476736 bytes) disk size: 17.9 GiB Child...

That is mine: ``` Drive Identifier 363D013C-D19F-44B7-8079-82EA063BB118 ImageName 95E3BDD3-62C7-4CA3-8FE1-BC046EBFC26A.qcow2 ReadOnly ``` Because of the ID difference I created a new clone from a working vm and then without starting UTM...

I did what you said but the file was not converted to to `qcow2`. UTM just copied the `raw`-File from the import location to the VM location.

https://docs.getutm.app/settings-qemu/drive/drive/ says: > When importing a drive that is non-removable and **not** a raw image, the selected image will first be converted to the QCOW2 format. So we cannot expect...

Bingo - macOS seems not to work with `qcow2` :( ``` ├── Debian 11 (LDXE).utm │   ├── Data │   │   ├── 64C60E7D-25B1-4AF0-AFDF-B12F5688E431.qcow2 │   │   └── efi_vars.fd │   └── config.plist ├──...

Snapshots with APFS are not sufficient. I want to restore the whole system. So I think I will have to clone the VM every time I need a snapshot. Not...