Windows 10 rather slow under UTM

[freebrowser1]

Describe the issue
Using Windows 10 I note that it performs rather slowly, unlike Linux VMs.
The same VM (qcow2 image is just converted from the vdi using qemu-img) is faster under VirtualBox.

Note: I sometimes compress the .qcow2 image using qemu-img -c which reduces it from 48GB to 19GB. Maybe that slows down performance ?
But doing the same with Linux VMs does not slow down performance.

Configuration

• UTM Version: 3.2.4
• OS Version: macOS 12.4
• Intel

Debug log

Running:  -L /Applications/UTM.app/Contents/Resources/qemu -S -qmp tcp:127.0.0.1:4001,server,nowait -nodefaults -vga none -spice "unix=on,addr=/Users/klaas/Library/Group Containers/WDNLXAD4W8.com.utmapp.UTM/DDC015C5-EAC1-46A0-A1EA-9B3F86EC1921.spice,disable-ticketing=on,image-compression=off,playback-compression=off,streaming-video=off,gl=off" -device virtio-vga -device virtio-rng-pci -smp cpus=4,sockets=1,cores=4,threads=1 -machine q35,vmport=off,i8042=off -accel hvf -accel tcg,thread=multi,tb-size=1024 -global PIIX4_PM.disable_s3=1 -global ICH9-LPC.disable_s3=1 -drive if=pflash,format=raw,unit=0,file=/Applications/UTM.app/Contents/Resources/qemu/edk2-x86_64-code.fd,readonly=on -drive "if=pflash,unit=1,file=/Users/klaas/Library/Containers/com.utmapp.UTM/Data/Documents/Windows XP Home.utm/Images/efi_vars.fd" -boot menu=on -m 4096 -device intel-hda -device hda-duplex -name "Windows XP Home" -usb -device usb-tablet,bus=usb-bus.0 -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -device nec-usb-xhci,id=usb-controller-0 -chardev spicevmc,name=usbredir,id=usbredirchardev0 -device usb-redir,chardev=usbredirchardev0,id=usbredirdev0,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2,bus=usb-controller-0.0 -device ide-cd,bus=ide.0,drive=cdrom0,bootindex=0 -drive if=none,media=cdrom,id=cdrom0 -device ide-hd,bus=ide.1,drive=drive0,bootindex=1 -drive "if=none,media=disk,id=drive0,file=/Users/klaas/Library/Containers/com.utmapp.UTM/Data/Documents/Windows XP Home.utm/Images/Windows XP.qcow2,cache=writethrough" -device e1000,mac=16:21:CE:93:FD:38,netdev=net0 -netdev vmnet-macos,mode=bridged,id=net0 -device virtio-serial -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,id=vdagent,debug=0,name=vdagent -device virtserialport,chardev=charchannel1,id=channel1,name=org.spice-space.webdav.0 -chardev spiceport,name=org.spice-space.webdav.0,id=charchannel1 -uuid DDC015C5-EAC1-46A0-A1EA-9B3F86EC1921 -rtc base=localtime
qemu-x86_64-softmmu: -netdev vmnet-macos,mode=bridged,id=net0: info: Started vmnet interface with configuration:
qemu-x86_64-softmmu: -netdev vmnet-macos,mode=bridged,id=net0: info: MTU:              1500
qemu-x86_64-softmmu: -netdev vmnet-macos,mode=bridged,id=net0: info: Max packet size:  1514
qemu-x86_64-softmmu: -netdev vmnet-macos,mode=bridged,id=net0: info: MAC:              72:0c:76:b4:df:d9
qemu-x86_64-softmmu: -netdev vmnet-macos,mode=bridged,id=net0: info: UUID:             BB55831F-8103-4109-9DEB-75D49BA2958A
qemu-x86_64-softmmu: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-x86_64-softmmu: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-x86_64-softmmu: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-x86_64-softmmu: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
qemu-x86_64-softmmu: warning: global PIIX4_PM.disable_s3=1 not used
qemu-x86_64-softmmu: warning: Spice: playback:0 (0x7f8f6d838950): setsockopt failed, Operation not supported on socket
qemu-x86_64-softmmu: warning: Spice: record:0 (0x7f8f6d838a00): setsockopt failed, Operation not supported on socket

What do these warnings mean ?
Upload VM

<?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>ConfigurationVersion</key>
	<integer>2</integer>
	<key>Debug</key>
	<dict>
		<key>DebugLog</key>
		<true/>
	</dict>
	<key>Display</key>
	<dict>
		<key>ConsoleBackgroundColor</key>
		<string>#000000</string>
		<key>ConsoleFont</key>
		<string>Menlo-Regular</string>
		<key>ConsoleFontSize</key>
		<integer>12</integer>
		<key>ConsoleOnly</key>
		<false/>
		<key>ConsoleTextColor</key>
		<string>#ffffff</string>
		<key>ConsoleTheme</key>
		<string>Default</string>
		<key>DisplayCard</key>
		<string>virtio-vga</string>
		<key>DisplayDownscaler</key>
		<string>linear</string>
		<key>DisplayUpscaler</key>
		<string>nearest</string>
	</dict>
	<key>Drives</key>
	<array>
		<dict>
			<key>DriveName</key>
			<string>cdrom0</string>
			<key>ImageType</key>
			<string>cd</string>
			<key>InterfaceType</key>
			<string>ide</string>
			<key>Removable</key>
			<true/>
		</dict>
		<dict>
			<key>DriveName</key>
			<string>drive0</string>
			<key>ImagePath</key>
			<string>Windows XP.qcow2</string>
			<key>ImageType</key>
			<string>disk</string>
			<key>InterfaceType</key>
			<string>ide</string>
		</dict>
		<dict>
			<key>DriveName</key>
			<string>driveBA2080B4-0461-4AFA-BFAF-C66E0F5F9B4E</string>
			<key>ImagePath</key>
			<string>efi_vars.fd</string>
			<key>ImageType</key>
			<string>none</string>
			<key>InterfaceType</key>
			<string></string>
		</dict>
		<dict>
			<key>DriveName</key>
			<string>driveD71EC6AD-1048-48C2-9BD0-48925CFA2BC7</string>
			<key>ImagePath</key>
			<string>Windows XPXX.qcow2</string>
			<key>ImageType</key>
			<string>none</string>
			<key>InterfaceType</key>
			<string></string>
		</dict>
	</array>
	<key>Info</key>
	<dict>
		<key>Icon</key>
		<string>windows</string>
	</dict>
	<key>Input</key>
	<dict>
		<key>InputInvertScroll</key>
		<true/>
		<key>InputLegacy</key>
		<false/>
	</dict>
	<key>Networking</key>
	<dict>
		<key>NetworkCard</key>
		<string>e1000</string>
		<key>NetworkCardMAC</key>
		<string>16:21:CE:93:FD:38</string>
		<key>NetworkMode</key>
		<string>bridged</string>
	</dict>
	<key>Printing</key>
	<dict/>
	<key>Sharing</key>
	<dict>
		<key>ClipboardSharing</key>
		<true/>
		<key>DirectoryReadOnly</key>
		<false/>
		<key>DirectorySharing</key>
		<true/>
		<key>Usb3Support</key>
		<true/>
		<key>UsbRedirectMax</key>
		<integer>3</integer>
	</dict>
	<key>Sound</key>
	<dict>
		<key>SoundCard</key>
		<string>intel-hda</string>
		<key>SoundEnabled</key>
		<true/>
	</dict>
	<key>System</key>
	<dict>
		<key>Architecture</key>
		<string>x86_64</string>
		<key>BootDevice</key>
		<string></string>
		<key>BootUefi</key>
		<true/>
		<key>CPU</key>
		<string>default</string>
		<key>CPUCount</key>
		<integer>4</integer>
		<key>ForceMulticore</key>
		<true/>
		<key>ForcePS2Controller</key>
		<false/>
		<key>Memory</key>
		<integer>4096</integer>
		<key>RTCUseLocalTime</key>
		<true/>
		<key>RngEnabled</key>
		<true/>
		<key>SystemUUID</key>
		<string>DDC015C5-EAC1-46A0-A1EA-9B3F86EC1921</string>
		<key>Target</key>
		<string>q35</string>
		<key>UseHypervisor</key>
		<true/>
	</dict>
</dict>
</plist>

[conath]

Did you install the UTM SPICE Guest tools for Windows?

[freebrowser1]

Yes, I did.

[ccalvocm]

Greetings @freebrowser1. I encountered the same issue in the past, but I resolved it by virtualizing Windows 11 ARM under UTM, which runs x86_64 apps seamlessly and supports GPU acceleration perfectly. I found that neither Windows 10/11 x86_64 nor Windows 10 ARM could run x86_64 apps.