January 24, 20251 yr @SimonF I'm having the same trouble with attempting a block commit on a VM snapshot. I get the dialog appear with no details which will never complete. A few days ago I upgraded to Unraid7 Stable and all has been well except now when wanting to commit to incorporate and remove the snapshots, it seems I cannot. My VM name in the UI has spaces and () in it "Home Assistant (HAOS)" but on disk, it is stored as /mnt/cachex/domains/HomeAssistant-HAOS/ When I attempt to run a block commit, it just hangs, regardless of the time I allow for it to run. The previous posts here that were similar seemed to be due to characters/spaces in the path but as far as I can tell, my path should be ok? Is there anything else I can do/look for to try and triage/resolve? Appreciate any help.
January 25, 20251 yr Author 9 hours ago, JNZ said: @SimonF I'm having the same trouble with attempting a block commit on a VM snapshot. I get the dialog appear with no details which will never complete. A few days ago I upgraded to Unraid7 Stable and all has been well except now when wanting to commit to incorporate and remove the snapshots, it seems I cannot. My VM name in the UI has spaces and () in it "Home Assistant (HAOS)" but on disk, it is stored as /mnt/cachex/domains/HomeAssistant-HAOS/ When I attempt to run a block commit, it just hangs, regardless of the time I allow for it to run. The previous posts here that were similar seemed to be due to characters/spaces in the path but as far as I can tell, my path should be ok? Is there anything else I can do/look for to try and triage/resolve? Appreciate any help. Would you be able to provide a copy of the XML when the VM is running? virsh dumpxml "Home Assistant (HAOS)" and also cat /etc/libvirt/qemu/snapshotdb/"Home Assistant (HAOS)"/snapshots.db
January 25, 20251 yr 42 minutes ago, SimonF said: Would you be able to provide a copy of the XML when the VM is running? virsh dumpxml "Home Assistant (HAOS)" and also cat /etc/libvirt/qemu/snapshotdb/"Home Assistant (HAOS)"/snapshots.db Thanks Simon, I have sent you the files across.
January 31, 20251 yr Hello All, When the VM is offline I can take a snapshot without any issues. However, when I try with the virtual machine online it gives me this error: Requested operation is not valid: cannot migrate domain: 0000:12:00.0: VFIO migration is not supported in kernel; 0000:12:00.1: VFIO migration is not supported in kernel; 0000:02:00.0: VFIO migration is not supported in kernel Does anyone know if there is a way to take a snapshot while the VM is running, I am doing some testing and want to make sure is not a configuration or a setting on the VM template. Any help is greatly appreciated. Thank you.
February 3, 20251 yr "Insufficent Storage for Snapshot" Can I tell it to Exclude a Passed Disk Hello All, I'm moving to using VM snapshots as opposed to ZFS. Really pleased with the UI so far and Windows/Debian have gone well BUT I could not run it on a Linux VM is use for my CCTV as there is Insufficent Storage for Snapshot. The VM's run on an NVME pool with 300+gb of free space so I am assuming its trying to include a 1TB drive I have passed through to the VM in the snapshot. Is there a way to exclude the passed drive?
February 18, 20251 yr "No related Snapshot file" Hello, I tried snapshots... I took 2 subsequent snapshots. But after I "Block Commit"ed the first with --base and (I think that was the fault) --top, it seems I have a zombie in my system. root@somehost:/etc/libvirt/qemu/snapshotdb/Win10 Main# cat snapshots.db { "Update-Feb-25-generate": { "name": "Update-Feb-25-generate", "parent": "", "state": "shutoff", "desc": null, "memory": { "@attributes": { "snapshot": "no" } }, "creationtime": "1738524397", "method": "QEMU", "backing": { "hdc": [ "\/mnt\/user\/domains\/Win10 Main\/vdisk1.img" ], "rhdc": [ "\/mnt\/user\/domains\/Win10 Main\/vdisk1.img" ] }, "primarypath": "\/mnt\/disk2\/domains\/Win10 Main", "disks": [ { "@attributes": { "name": "hdc", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/user\/domains\/Win10 Main\/vdisk1.Update-Feb-25-generateqcow2" } } }, { "@attributes": { "name": "hda", "snapshot": "no" } }, { "@attributes": { "name": "hdb", "snapshot": "no" } } ] } but the only file in the folder \/mnt\/user\/domains\/Win10 Main\ is vdisk1.img. Also in the gui, the related img is vdisk1.img: When I run the VM it shows the last state i had when I last shut it down ( which was way after the 2nd snapshot). What can I do with the snapshot? Is it still rlevant? Can I safely delete it? Thanks for advice.
February 18, 20251 yr Author 1 hour ago, ridikuel said: "No related Snapshot file" Hello, I tried snapshots... I took 2 subsequent snapshots. But after I "Block Commit"ed the first with --base and (I think that was the fault) --top, it seems I have a zombie in my system. root@somehost:/etc/libvirt/qemu/snapshotdb/Win10 Main# cat snapshots.db { "Update-Feb-25-generate": { "name": "Update-Feb-25-generate", "parent": "", "state": "shutoff", "desc": null, "memory": { "@attributes": { "snapshot": "no" } }, "creationtime": "1738524397", "method": "QEMU", "backing": { "hdc": [ "\/mnt\/user\/domains\/Win10 Main\/vdisk1.img" ], "rhdc": [ "\/mnt\/user\/domains\/Win10 Main\/vdisk1.img" ] }, "primarypath": "\/mnt\/disk2\/domains\/Win10 Main", "disks": [ { "@attributes": { "name": "hdc", "snapshot": "external", "type": "file" }, "driver": { "@attributes": { "type": "qcow2" } }, "source": { "@attributes": { "file": "\/mnt\/user\/domains\/Win10 Main\/vdisk1.Update-Feb-25-generateqcow2" } } }, { "@attributes": { "name": "hda", "snapshot": "no" } }, { "@attributes": { "name": "hdb", "snapshot": "no" } } ] } but the only file in the folder \/mnt\/user\/domains\/Win10 Main\ is vdisk1.img. Also in the gui, the related img is vdisk1.img: When I run the VM it shows the last state i had when I last shut it down ( which was way after the 2nd snapshot). What can I do with the snapshot? Is it still rlevant? Can I safely delete it? Thanks for advice. Do the override files still exist in the VM Directory?
February 19, 20251 yr 9 hours ago, SimonF said: Do the override files still exist in the VM Directory? root@somehost:~# ll /mnt/user/domains/Win10\ Main/ total 114G drwxr-xr-x 1 nobody users 32 Feb 18 13:02 ./ drwxrwxrwx 1 nobody users 57 Dec 18 2023 ../ -rwxrwxrwx 1 root root 114G Feb 18 13:23 vdisk1.img* root@somehost:~# ll /etc/libvirt/qemu/snapshotdb/Win10\ Main/ total 4.0K drwxr-xr-x 1 root root 24 Feb 1 21:09 ./ drwxr-xr-x 1 root root 20 Feb 1 21:09 ../ -rw-r--r-- 1 root root 1.5K Feb 18 13:02 snapshots.db root@somehost:~# ll /etc/libvirt/qemu/snapshot/ total 0 drwxr-xr-x 1 root users 0 Feb 3 16:46 ./ drwxr-xr-x 1 root root 152 Feb 18 13:02 ../ root@somehost:~# Sorry, idk what overrride files are. Hope my answer above helps.
February 19, 20251 yr Author 10 hours ago, ridikuel said: root@somehost:~# ll /mnt/user/domains/Win10\ Main/ total 114G drwxr-xr-x 1 nobody users 32 Feb 18 13:02 ./ drwxrwxrwx 1 nobody users 57 Dec 18 2023 ../ -rwxrwxrwx 1 root root 114G Feb 18 13:23 vdisk1.img* root@somehost:~# ll /etc/libvirt/qemu/snapshotdb/Win10\ Main/ total 4.0K drwxr-xr-x 1 root root 24 Feb 1 21:09 ./ drwxr-xr-x 1 root root 20 Feb 1 21:09 ../ -rw-r--r-- 1 root root 1.5K Feb 18 13:02 snapshots.db root@somehost:~# ll /etc/libvirt/qemu/snapshot/ total 0 drwxr-xr-x 1 root users 0 Feb 3 16:46 ./ drwxr-xr-x 1 root root 152 Feb 18 13:02 ../ root@somehost:~# Sorry, idk what overrride files are. Hope my answer above helps. Sorry I mean overlay they appear in the VM directory to hold changes from the base file. Looks like there are no files you can delete using the gui or remove the snapshots.db file. Not sure why it has not removed the entry. I will look to see if I can replicate and fix if I find an issue,
March 2, 20251 yr Ok, this is a weird issue, I created a snapshot through the GUI, the name has spaces and I can not revert to the snapshot now. There is no option in the GUI and virsh does not see the snapshot due to the name. I need to revert the VM due to a failed change. I cant find any examples of snapshots with spaces to see how to correctly specify the snapshot Edited March 2, 20251 yr by hwextreme
March 2, 20251 yr Author 41 minutes ago, hwextreme said: Ok, this is a weird issue, I created a snapshot through the GUI, the name has spaces and I can not revert to the snapshot now. There is no option in the GUI and virsh does not see the snapshot due to the name. I need to revert the VM due to a failed change. I cant find any examples of snapshots with spaces to see how to correctly specify the snapshot You can stop the VM if start and just change the disks back to vdisk1.img and vdisk2.img. The new files are overlays for changes. Process does not use internal snapshots hence why they don't show.
March 3, 20251 yr Thanks SimonF I have the VM up and running now by changing the disks back to the original, I will do some more testing with snapshot creation through cmd line instead of the gui (without spaces) although I will have to rebuild this VM as I had expected the snapshot to work the same way as Vmware which would revert configuration changes to the VM. It seems that the network adapter setting I changed, are not reverting properly and both now believe they are on the same VLAN when they are actually different VLANS, but that will be another discussion
April 23, 20251 yr Hi friends, I want to use snapshot for VM but when I do it, I can see only that it was done, see picture, but I have no option to see snapshots and recover it as I can see on your pictures above. What is my problem please? Many thanks Vladimir
April 23, 20251 yr Author 28 minutes ago, VladoB said: Hi friends, I want to use snapshot for VM but when I do it, I can see only that it was done, see picture, but I have no option to see snapshots and recover it as I can see on your pictures above. What is my problem please? Many thanks Vladimir Click on VM name to expand details
April 23, 20251 yr Thanks a lot Simon, indeed it is now clear. can you please advice, what it means that Guest not installed? Is it necessary to install something into Windows so that all is OK?
April 23, 20251 yr Author 42 minutes ago, VladoB said: Thanks a lot Simon, indeed it is now clear. can you please advice, what it means that Guest not installed? Is it necessary to install something into Windows so that all is OK? You need to install guest agent from the virtio cd. But is only required to so guest IP addresses
June 20, 20251 yr 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: ---baseTop image: ---topPivot: checkedDelete: checkedIn 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.
June 21, 20251 yr Author 11 hours ago, impoftheperverse said: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: ---baseTop image: ---topPivot: checkedDelete: checkedIn 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.Can you provide output of qemu-img info --backing-chain -U filenamecan you can /etc/libvirt/qemu/snapshotdb/Windows \ 11/snapshots.dband virsh dumpxml "Windows 11" with the VM running.Are you using a unassigned device as the /disks path is normally associated with that.
June 21, 20251 yr 2 hours ago, SimonF said:Can you provide output of qemu-img info --backing-chain -U filenameThis 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 GiB2 hours ago, SimonF said:Are you using a unassigned device as the /disks path is normally associated with that.Yes, this is an NVME unassigned devide disk where only the VM image is stored2 hours ago, SimonF said:can you can /etc/libvirt/qemu/snapshotdb/Windows \ 11/snapshots.dband virsh dumpxml "Windows 11" with the VM running.(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> Edited June 21, 20251 yr by impoftheperverse
June 21, 20251 yr Author 1 hour ago, impoftheperverse said:(Not sure about what you meant to do with the snapshots.db)Should be cat /etc/Libvirt/qemu/snapshotdb/........
June 21, 20251 yr 5 hours ago, SimonF said:Should be cat /etc/Libvirt/qemu/snapshotdb/........ 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" } } ] }
June 21, 20251 yr Author 1 hour ago, impoftheperverse said: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" } } ] }Info look ok,can you just run qemu-img info --backing-chain /mnt/disks/S7GDNS0X310934J/Windows\ 11/vdisk-w11.S20250614155524qcow2Just to check it shows the backng file.
June 21, 20251 yr 5 hours ago, SimonF said:Info look ok,can you just run qemu-img info --backing-chain /mnt/disks/S7GDNS0X310934J/Windows\ 11/vdisk-w11.S20250614155524qcow2Just to check it shows the backng file.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
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.