impoftheperverse

I tried again and it was successful. The only difference with the previous attempt was that this time all the VMs were turned off. The time it failed, the VM that was turned on was using the 2 USB devices attached to the VM that had the snapshot. Probably it did not have anything to do, but just in case someone has the same issue, it's worth trying. Thanks a lot for your help, SimonF.

I will try again tonight. This time with all the VMs turned off and not only the one that had the snapshot. Could you let me know what the "pivot" option does?

Sure: qemu-img info --backing-chain /mnt/disks/S7GDNS0X310934J/Windows\ 11/vdisk-w11.S20250614155524qcow2 image: /mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.S20250614155524qcow2 file format: qcow2 virtual size: 600 GiB (644245094400 bytes) disk size: 95.3 GiB cluster_size: 65536 backing file: /mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.img backing file format: raw Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false extended l2: false Child node '/file': filename: /mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.S20250614155524qcow2 protocol type: file file length: 95.3 GiB (102318800896 bytes) disk size: 95.3 GiB image: /mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.img file format: raw virtual size: 600 GiB (644245094400 bytes) disk size: 598 GiB Child node '/file': filename: /mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.img protocol type: file file length: 600 GiB (644245094400 bytes) disk size: 598 GiB

Here it is: cat /etc/libvirt/qemu/snapshotdb/Windows\ 11/snapshots.db { "S20250614155524": { "name": "S20250614155524", "parent": "Base", "state": "shutoff", "desc": "250614", "memory": { "@attributes": { "snapshot": "no" } }, "creationtime": "1749909324", "method": "QEMU", "backing": { "hdc": [ "\/mnt\/disks\/S7GDNS0X310934J\/Windows 11\/vdisk-w11.S20250614155524qcow2", "\/mnt\/disks\/S7GDNS0X310934J\/Windows 11\/vdisk-w11.img" ], "rhdc": [ "\/mnt\/disks\/S7GDNS0X310934J\/Windows 11\/vdisk-w11.img", "\/mnt\/disks\/S7GDNS0X310934J\/Windows 11\/vdisk-w11.S20250614155524qcow2" ] }, "primarypath": "\/mnt\/disks\/S7GDNS0X310934J\/Windows 11", "disks": [ { "@attributes": { "name": "hdc", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/disks\/S7GDNS0X310934J\/Windows 11\/vdisk-w11.S20250614155524qcow2" } } }, { "@attributes": { "name": "hdb", "snapshot": "no" } } ] }

This is the quemu-img info: qemu-img info --backing-chain /mnt/disks/S7GDNS0X310934J/Windows\ 11/vdisk-w11.img image: /mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.img file format: raw virtual size: 600 GiB (644245094400 bytes) disk size: 598 GiB Child node '/file': filename: /mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.img protocol type: file file length: 600 GiB (644245094400 bytes) disk size: 598 GiB Yes, this is an NVME unassigned devide disk where only the VM image is stored (Not sure about what you meant to do with the snapshots.db) But here is the virsh dumpxml: <domain type='kvm' id='21'> <name>Windows 11</name> <uuid>941baef8-ca09-5b26-bb49-f112b1fdde4e</uuid> <metadata> <vmtemplate xmlns="http://unraid" name="Windows 11" icon="windows11.png" os="windowstpm" iconold="windows11.png" webui=""/> </metadata> <memory unit='KiB'>51904512</memory> <currentMemory unit='KiB'>51904512</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>28</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='21'/> <vcpupin vcpu='8' cpuset='6'/> <vcpupin vcpu='9' cpuset='22'/> <vcpupin vcpu='10' cpuset='7'/> <vcpupin vcpu='11' cpuset='23'/> <vcpupin vcpu='12' cpuset='8'/> <vcpupin vcpu='13' cpuset='24'/> <vcpupin vcpu='14' cpuset='9'/> <vcpupin vcpu='15' cpuset='25'/> <vcpupin vcpu='16' cpuset='10'/> <vcpupin vcpu='17' cpuset='26'/> <vcpupin vcpu='18' cpuset='11'/> <vcpupin vcpu='19' cpuset='27'/> <vcpupin vcpu='20' cpuset='12'/> <vcpupin vcpu='21' cpuset='28'/> <vcpupin vcpu='22' cpuset='13'/> <vcpupin vcpu='23' cpuset='29'/> <vcpupin vcpu='24' cpuset='14'/> <vcpupin vcpu='25' cpuset='30'/> <vcpupin vcpu='26' cpuset='15'/> <vcpupin vcpu='27' cpuset='31'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash' format='raw'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram format='raw'>/etc/libvirt/qemu/nvram/941baef8-ca09-5b26-bb49-f112b1fdde4e_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='off'> <topology sockets='1' dies='1' clusters='1' cores='14' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback' discard='ignore'/> <source file='/mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.S20250614155524qcow2' index='2'/> <backingStore type='file' index='3'> <format type='raw'/> <source file='/mnt/disks/S7GDNS0X310934J/Windows 11/vdisk-w11.img'/> <backingStore/> </backingStore> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0d' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu'/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='3' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='3'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='4' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='4'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <controller type='pci' index='5' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='5'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller> <controller type='pci' index='6' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='6'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </controller> <controller type='pci' index='7' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='7'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0e:61:cd'/> <source bridge='br0'/> <target dev='vnet19'/> <model type='e1000'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/run/libvirt/qemu/channel/21-Windows 11/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0xfa56'/> <address bus='1' device='2'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04f2'/> <product id='0x0841'/> <address bus='1' device='3'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

Hello there! I tried to find this information in the documentation, but without success. I have a Windows 11 VM and I created a snapshot a few days ago. Now I have two image files: the base file (vdisk.img) and the overlay with the changes (vdisk-superlongname). I don't need the snapshot anymore, so I clicked "block commit" for all the overlay changes to be written into the original vdisk.img and the snapshot be removed. The settings I set in the dialog window are: Base image: ---base Top image: ---top Pivot: checked Delete: checked In the scrolldown for base and top the only selectable option is the name of the snapshot (in both of them). After I click "Action", I get this error message: The VM was turned off both at the time of the snapshot and at the time I tried to block commit. I also found this in the libvirt log, which is weird, because at the same time I block commited, it seems like Unraid was looking for the USB devices attached to the VM (which were in use by another VM): Any idea of what's going wrong?? Help is much appreciated. Thanks! Regards.

Hello there! I tried to find this information in the documentation, but without success. I have a Windows 11 VM and I created a snapshot a few days ago. Now I have two image files: the base file (vdisk.img) and the overlay with the changes (vdisk-superlongname). I don't need the snapshot anymore, so I clicked "block commit" for all the overlay changes to be written into the original vdisk.img and the snapshot be removed. The settings I set in the dialog window are: Base image: ---base Top image: ---top Pivot: checked Delete: checked In the scrolldown for base and top the only selectable option is the name of the snapshot (in both of them). After I click "Action", I get this error message: what am I doing wrong?? Help is much appreciated. Thanks! Regards. Edit: I did not mention that the VM was turned off both at the time of the snapshot and at the time I tried to block commit. I also found this in the libvirt log, which is weird, because at the same time I block commited, it seems like Unraid was looking for the USB devices attached to the VM (which were in use by another VM):

Thanks, Jorge. Here are the 3 syslog files that were stored in the USB after each time the server became unreachable. After the last time I posted I followed a post you wrote somewhere else about this problem happening with Raizen CPUs (which is my case). I changed the BIOS settings (as per your advice) and for now the server has been up and running without an issue. However, still I'd like to know if there's something in the log which can point at a different issue... just to close this chapter which has been going on for a long time. Thanks! syslog-previous syslog-previous2 syslog-previous3

After those marvelous 3 weeks that the random crash did not happened, it's going on again every couple of days. I managed to gather some of the syslog-previous from just after the crash/unresponsive/unreachable status. Is there any information I should hide from the syslog files before posting here? Thanks!

After two months of random disconnections, ever since I enabled the syslog server (mirror to flash) it did not happen again (3 weeks and running). Does this make any sense? Should I disable syslog server and see what happens or it is 100% certain that it can't have anything to do with it and it's not worth the try?

Thanks, JorgeB. I'll do that and share the diagnostics when the error happens again.

I'm using Unraid 6.12.15 and from time to time, completely at a random interval which ranges from 24 hours to a whole week, I'm unable to access the server IP. I've tried restarting the router and replacing the Ethernet cable, but the only thing that works when that happens is a hard reboot. Since I can't access the server until after rebooting, the only diagnosis file that I can attach is just after the restart. On a side note, I've noticed that the connection is never lost when a VM is running. This does not mean that it can't happen, but for about a couple of months it never occurred while a VM was running. This is becoming a huge problem and I would appreciate a lot if someone could point me in the right direction to fix this problem. Thanks in advance for your help. impvault-diagnostics-20250403-0856.zip

Thank you once again. Everything was solved. Not sure if it was related, but before this happened I physically removed an old GPU and 2 (unassigned) ssd drives from the server case. I suppose the problem with the SATA controller being passed through had somehow something to do with that.

I removed that code from the VM which was causing the issue, and I also checked the other 2. However, when I rebooted, without even starting the VMs, the vfio-pci log shows that the controller is still being binded. I attached full diagnostics. Btw. when I rebooted a warning poped up saying "VM Autostart disabled due to vfio-bind error". I don't have any of my VMs in autostart... Loading config from /boot/config/vfio-pci.cfg BIND=0000:09:00.0|10de:1e84 0000:09:00.1|10de:10f8 0000:09:00.2|10de:1ad8 0000:09:00.3|10de:1ad9--- Processing 0000:09:00.0 10de:1e84 --- Processing 0000:09:00.1 10de:10f8 --- Processing 0000:09:00.2 10de:1ad8 --- Processing 0000:09:00.3 10de:1ad9 --- Devices listed in /sys/bus/pci/drivers/vfio-pci: vfio-pci binding complete impvault-diagnostics-20241127-1900.zip

Thanks a lot, Jorge, for having a look at it. Could you point me in the right direction as to how to prevent that controller from being passed through to the VM? I follow lots of tutorials, but my understanding of how things works is pretty shallow... Sorry. (In case it's important, I'm using PCIe ACS Override in system devices, as that is the only way I can pass through my GPU) PS. once that is solved, should I stop/start the array and perform a parity check or how do I get parity enabled again? Thanks!