Unable to create snapshot.

[JanR27]

Hi!

Every time I try to create a snapshot, I get this error:

"CLIENT ERROR: TUINSRemoteViewController does not override -viewServiceDidTerminateWithError: and thus cannot react to catastrophic errors beyond logging them"

Is it possible that this error appears, since my vm is on a SD Card?

[Metamogul]

Hey @JanR27, I'm sorry to hear that. The message sounds unfamiliar though. Could you please provide a precise description of the state of the app you're in before the error occurs, the action you're performing that is leading to the error message, and the following, undesired behaviour of the app? Also include your system architecture as reported by the arch command, the MacOS version you're on as reported by sw_vers, the XCode-Version you've been using as reported by xcodebuild -version as well as any other information that seems relevant to you.

[paulpv]

I don't know if this is 100% related, but:

Brand new M4 Pro with latest xcode and UTM-Snapshot-Manager code.

% xcodebuild -version
Xcode 16.1
Build version 16B40

Screen.Recording.2024-11-14.at.4.19.04.PM.mp4

config.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Backend</key>
	<string>QEMU</string>
	<key>ConfigurationVersion</key>
	<integer>4</integer>
	<key>Display</key>
	<array>
		<dict>
			<key>DownscalingFilter</key>
			<string>Linear</string>
			<key>DynamicResolution</key>
			<false/>
			<key>Hardware</key>
			<string>qxl-vga</string>
			<key>NativeResolution</key>
			<false/>
			<key>UpscalingFilter</key>
			<string>Linear</string>
		</dict>
	</array>
	<key>Drive</key>
	<array>
		<dict>
			<key>Identifier</key>
			<string>0</string>
			<key>ImageName</key>
			<string>QEMU_EFI-X64-iPad-UTM-logo.fd</string>
			<key>ImageType</key>
			<string>Disk</string>
			<key>Interface</key>
			<string>PFlash</string>
			<key>InterfaceVersion</key>
			<integer>0</integer>
			<key>ReadOnly</key>
			<false/>
		</dict>
		<dict>
			<key>Identifier</key>
			<string>1</string>
			<key>ImageName</key>
			<string>disk-0.qcow2</string>
			<key>ImageType</key>
			<string>Disk</string>
			<key>Interface</key>
			<string>VirtIO</string>
			<key>InterfaceVersion</key>
			<integer>0</integer>
			<key>ReadOnly</key>
			<false/>
		</dict>
		<dict>
			<key>Identifier</key>
			<string>2</string>
			<key>ImageType</key>
			<string>CD</string>
			<key>Interface</key>
			<string>USB</string>
			<key>InterfaceVersion</key>
			<integer>0</integer>
			<key>ReadOnly</key>
			<true/>
		</dict>
		<dict>
			<key>Identifier</key>
			<string>E4E29B81-6630-4629-9076-BB27DB46869C</string>
			<key>ImageName</key>
			<string>E4E29B81-6630-4629-9076-BB27DB46869C.qcow2</string>
			<key>ImageType</key>
			<string>Disk</string>
			<key>Interface</key>
			<string>NVMe</string>
			<key>InterfaceVersion</key>
			<integer>1</integer>
			<key>ReadOnly</key>
			<false/>
		</dict>
	</array>
	<key>Information</key>
	<dict>
		<key>Icon</key>
		<string>windows</string>
		<key>IconCustom</key>
		<false/>
		<key>Name</key>
		<string>Windows 10 x64</string>
		<key>UUID</key>
		<string>3C4A8FB7-DD94-4A0C-9B04-5CDD2392CC8A</string>
	</dict>
	<key>Input</key>
	<dict>
		<key>MaximumUsbShare</key>
		<integer>3</integer>
		<key>UsbBusSupport</key>
		<string>2.0</string>
		<key>UsbSharing</key>
		<true/>
	</dict>
	<key>Network</key>
	<array/>
	<key>QEMU</key>
	<dict>
		<key>AdditionalArguments</key>
		<array/>
		<key>BalloonDevice</key>
		<false/>
		<key>DebugLog</key>
		<false/>
		<key>Hypervisor</key>
		<false/>
		<key>PS2Controller</key>
		<true/>
		<key>RNGDevice</key>
		<true/>
		<key>RTCLocalTime</key>
		<true/>
		<key>TPMDevice</key>
		<false/>
		<key>TSO</key>
		<false/>
		<key>UEFIBoot</key>
		<false/>
	</dict>
	<key>Serial</key>
	<array/>
	<key>Sharing</key>
	<dict>
		<key>ClipboardSharing</key>
		<false/>
		<key>DirectoryShareMode</key>
		<string>None</string>
		<key>DirectoryShareReadOnly</key>
		<false/>
	</dict>
	<key>Sound</key>
	<array>
		<dict>
			<key>Hardware</key>
			<string>ich9-intel-hda</string>
		</dict>
	</array>
	<key>System</key>
	<dict>
		<key>Architecture</key>
		<string>x86_64</string>
		<key>CPU</key>
		<string>qemu64-v1</string>
		<key>CPUCount</key>
		<integer>4</integer>
		<key>CPUFlagsAdd</key>
		<array/>
		<key>CPUFlagsRemove</key>
		<array/>
		<key>ForceMulticore</key>
		<true/>
		<key>JITCacheSize</key>
		<integer>512</integer>
		<key>MemorySize</key>
		<integer>1024</integer>
		<key>Target</key>
		<string>q35</string>
	</dict>
</dict>
</plist>

Windows 10 x64.utm was pulled from wayback machine shown in this video:
https://youtu.be/KsNoGPczavw

[paulpv]

Just a guess, maybe my issue is because I am using emulated NVMe?
In UTM when I try to close the VM:

NOTE that this is in Emulate mode (Mac M4 Pro CPU emulating x64), not Virtualize mode.

[paulpv]

pv@Pauls-MacBook-Pro-M4-Pro Virtual Machines.localized % cd Windows\ 10\ x64.utm 
pv@Pauls-MacBook-Pro-M4-Pro Windows 10 x64.utm % ls -la
total 368
drwxr-xr-x@  5 pv  staff     160 Nov 14 06:08 .
drwxr-xr-x  14 pv  staff     448 Nov 14 05:56 ..
drwxr-xr-x@  5 pv  staff     160 Nov 14 06:08 Data
-rw-r--r--@  1 pv  staff    3497 Nov 14 06:08 config.plist
-rw-r--r--@  1 pv  staff  182349 Nov 14 16:39 screenshot.png
pv@Pauls-MacBook-Pro-M4-Pro Windows 10 x64.utm % cd Data 
pv@Pauls-MacBook-Pro-M4-Pro Data % ls -la
total 22073184
drwxr-xr-x@ 5 pv  staff          160 Nov 14 06:08 .
drwxr-xr-x@ 5 pv  staff          160 Nov 14 06:08 ..
-rw-r--r--@ 1 pv  staff  11299192832 Nov 14 16:36 E4E29B81-6630-4629-9076-BB27DB46869C.qcow2
-rw-r--r--@ 1 pv  staff      3653632 Mar  2  2021 QEMU_EFI-X64-iPad-UTM-logo.fd
-rw-r--r--@ 1 pv  staff       393216 Mar 12  2021 disk-0.qcow2
pv@Pauls-MacBook-Pro-M4-Pro Data % qemu-img snapshot E4E29B81-6630-4629-9076-BB27DB46869C.qcow2 -c Fresh\ Install
pv@Pauls-MacBook-Pro-M4-Pro Data % qemu-img snapshot E4E29B81-6630-4629-9076-BB27DB46869C.qcow2 -l               
Snapshot list:
ID      TAG               VM_SIZE                DATE        VM_CLOCK     ICOUNT
1       Fresh Install         0 B 2024-11-14 16:43:46  0000:00:00.000          0
pv@Pauls-MacBook-Pro-M4-Pro Data % 

[Metamogul]

Hey Paul! It looks like you‘ve reported to the wrong repo. This is just a POC for a snapshot manager for UTM and no official part of the UTM project. To report a bug there, please refer to the [official UTM project page here on GitHub] (https://github.com/utmapp/UTM). I’d recommend including a description that helps the devs reproducing the bug.

[paulpv]

Hey Paul! It looks like you‘ve reported to the wrong repo. This is just a POC for a snapshot manager for UTM and no official part of the UTM project. To report a bug there, please refer to the [official UTM project page here on GitHub] (https://github.com/utmapp/UTM). I’d recommend including a description that helps the devs reproducing the bug.

I wasn't reporting a problem with UTM.
I was confirming a similar problem to this Issue's problem with UTM-Snapshot-Manager not taking snapshots.

[Metamogul]

Sorry for the misunderstanding @paulpv. Could you provide a detailed description of what actions you're taking, what you expect to happen and what happens instead, as well as any relevant circumstantial info (e.g. configuration of the VMs drives, URLs of resources used, a copy of the VM if it doesn't contain sensitive information)? Please understand that I'm doing this project in my free time and I'm lacking the resources to diagnose by watching videos, guessing or experimenting.
In your video, I can see you using the Snapshot Manager, and it looks like you're expecting a drive for snapshotting to show up, yet there's none. Is that the issue you want to report? I'm asking this trying to understand if and how your issue is related to the problem reported in the ticket which describes a specific error message, and if and how your problem could be fixed.