SimonF

Does it show in lspci and the ID is the same?

What does nvidia-smi show?

pivot means that it will wait for the data be added into original file and when complete change the VM to that file and remove the overlay.

Feature was added in 7.1 for this. You can choose vCPUs without pinning.

Unsure what you are requesting.

Copy and paste needs to be enabled and you also need to load vdagent from spice. novnc from the console does not install anything on the VM so installing a servers should be ok.

If you know the values you need then you can set via SMBIOS in the qemu args.

Trying to reproduce, created a VM on UD, but work ok for me.

Also active snapshots will passthru is not really supported by qemu and kernel currently.

Do you have copy paste enabled? The vdagent is required to support. 7.1 was the initial implementation of snaps and was GUI based.

Post diagnostics.

Strange as it says all activity for me.

To create any snapshot from the VM Icon create snapshot with the VM running. Snapshots are stored in the VM directory as the method creates an overlay file for the changes with the base file of the orignal. Note some of my paths are non standard as this is a dev system. To rollback from the snapshots click on the icon and the menu appears. Revert will return to the previous setup. Block commit push changes in the overlay file back into the orginal. Pull pulls the base file into the overlay to create a new standalone file. There are no options currently to allow this as there is no command available to be added to a script. Functions will be added to the new API in future releases to support but no current time frame. Note reverting an active snapshot will return the VM to the running state when the snap was taken.

Info look ok, can you just run qemu-img info --backing-chain /mnt/disks/S7GDNS0X310934J/Windows\ 11/vdisk-w11.S20250614155524qcow2 Just to check it shows the backng file.

Choice is yours. Ether will be ok

Should be cat /etc/Libvirt/qemu/snapshotdb/........

Its now the little doc on the right.

Can you provide output of qemu-img info --backing-chain -U filename can you can /etc/libvirt/qemu/snapshotdb/Windows \ 11/snapshots.db and virsh dumpxml "Windows 11" with the VM running. Are you using a unassigned device as the /disks path is normally associated with that.

libvirt network names where added for 7.1 but there was a bug which was also fixed. They are the same as virbrx but will the real names.

Unraid is running kernel 6.12 which is greater than 6.2 so I should have the CVE patched.

If the services is enabled should saying running. what is the output of cat /var/log/syslog | grep -i wol

Use the WOL for services plugin. Allows starting,resume VM, docker etc

Maybe down to different refresh rates will look to see if any things can be done.

Fix was only for isos files will look into doing for vidsks.

There was a bug pre 7 that would get the size of a disk which would spin up drives but that was fixed. Maybe something else has changed will look into it. To confirm it happens on either the Dash or VM tab? I am not sure why the file is being open thou.