I will attach diagnostics in case it's needed. I tried rebooting the entire server but the same issue. Not sure what to do (I have snapshots but before I do anything, waiting for instructions) - The vm in VNC mode starts but the spinning white circle just stops. In VM's it shows paused but i did hard shut down and rebooted entire server and it keeps happening.

tower-diagnostics-20260611-1715.zip

Edited June 11Jun 11 by GeorgeJetson20

I guess since no one has responded, it's really broken ???

When you say you did a "hard shut down", do you mean you force stopped the VM or did you do a hard shut down of the server? According to the libvirt log there's a IO error:

26-06-11 21:10:12.964+0000: 30553: warning : qemuProcessHandleIOError:976 : Transitioned guest Windows 10 (work) to paused state due to IO error

Have you made any changes to the VM template lately? Removed devices or attached new devices? Do you have a backup of the libvrt.img? Maybe you can try to restore it if you have one.

Edit: One more clue(?) in the quemu log: 2026-06-11 21:10:12.964+0000: IO error device='virtio-disk2' node-name='libvirt-3-format' reason='No space left on device'

Looks like one of the disks attached to the VM is full. Try removing all disks except the windows.vdisk and see if it starts.

Edited June 13Jun 13 by strike

It was fully working in the morning and up... Walked away for 3 hours and it was not running anymore and i had to force shutdown the VM because it was getting this message when I clicked the pause (to try to resume, but i never saw that message before). It was saying something about Nginx is not valid and I got this message. I didn't try to restore snapshots to do anything because i didn't want to make it worse.. You mentioned no space on drive. But what is weird is that I have 1 TB SSD and this is 250G and I have another 250G for another VM and its fully running still - Are the snapshots taking alot of space?? If the actually data on the drive is 88G, is each snapshot also 88G ?? that would explain some of the space and probably can delete a snapshot.. let me know if im on the right track or not?

I figured to try this but I get this message when trying to delete the most recent snapshot. I don't quite understand how the snapshots work on unraid because it does not work the way VMware does the snapshots. This is the message I get when trying to remove most recent.. I am afraid to break it worse.,

The size of the snapshots depends on how much data changes over time and can very well grow to the same size as the vdisk itself. The more I look at it, it definitely looks like the "no space error" is the culprit. Could you stop the VM and run this on the terminal: qemu-img check -f qcow2 "/mnt/nvme/VMs/Windows 11/vdisk1.31-05-2026--generateqcow2" (replace with your path to the vdisk)

Here is some info I just googled about snapshots

1. Initial Size: At creation, a snapshot only requires about a few megabytes of metadata overhead.

2. Write Activity: As the VM runs and new data is written or modified, the snapshot records these "deltas" (changes). If you change 5GB of data, your snapshot grows by 5GB.

3. State vs. Disk: If you take an external or internal snapshot of just the disk, space only scales with disk writes. If you also snapshot the active VM memory (RAM), it will add the exact size of your assigned RAM to the snapshot size.

4. Growth Limits: The maximum theoretical size of a snapshot is the total size of your virtual hard disk, plus the size of the VM's RAM.

• Internal Snapshots: All state data and disk changes are bundled and saved directly inside the original .qcow2 disk image file.

• External Snapshots: Changes are saved to a new overlay file (called a backing chain), while the original .qcow2 file remains untouched. These overlay files are typically stored in the default image directory: /var/lib/libvirt/images/

• Temporary Snapshots: If you pass the -snapshot flag directly to QEMU, changes are stored in temporary files usually placed in /tmp/ or /var/tmp/ until the VM shuts down.

You should also check out these links for more on snapshots and how to manage them on unraid:

https://docs.unraid.net/unraid-os/using-unraid-to/create-virtual-machines/vm-setup/#vm-snapshots

https://forums.unraid.net/topic/191371-is-there-any-documentation-or-tutorial-on-unraid-7-snapshots/

Edit: It could also be wise to check where your libvirt.img file is stored (in the system share by default) and check that the space is sufficient on that drive.

Edited June 13Jun 13 by strike

Strike,

My libvirt is in system which is normal, i think you asked that.

Here is the results of the line from terminal:

qemu-img check -f qcow2 "/mnt/disks/S6PTNM0TA06285F/Windows 10 (work)/vdisk1.May2005qcow2

I tried to remove the oldest snapshot but for all the snapshots, I get this message - But it's not running for certain. Let me know what else I can possibly do to get this going.

Can anyone else help? I am not able to boot the VM at all. I am kind of stuck and not how to remedy this.

This is resolved by restoring a urbackup backup onto another drive but then ran into a problem where windows was saying not activated, needed to copy the original UUID and MAC address over to new backup and update the NVAR template line and now fully back online but wish I knew the real reason the problem occurred in the first place