Hi unman et al, On 2025-10-20 12:42, 'unman' via qubes-users wrote:
HiI dont use btrfs, but I do backup some qubes while they are running, by mounting the private.img and private-snap volumes. I think this is what you are proposing, and it will work fine. Mount the volume ro. I use a disposable to take the backup of the qube, and spawn it for each new volume. It works well, and I dont have issues.
Good idea with the disposable for each container!
private.img is the file that contains /rw for your qube. The timestamped entries are backups of your private.img. You can revert to these as you will. I dont recognise private-dirty. Sorry.
private-dirty.img looks like to be my currently running vm image, instead of your private-snap.img which I am missing on my system. My private-dirty.img is a mountable blockdevice-file too. I try to attach the private.img containerfiles to a VM. I already learned [1] that directly attaching a containerfile from within the qubes vm path (/var/lib/qubes/appvms/) is blocked. So I take a snapshot and rename "appvms" to "appvms_working", and try to attach this private.img to my backup-vm. The first step, losetup, works, the device is created.. The second step, the actual attaching, then fails: $ sudo losetup -f --show "/snapshots/2025-10-21/appvms_working/sys-usb/private.img" /dev/loop10 $ sudo losetup --all | grep loop10 /dev/loop10: [0061]:18762 (/snapshots/2025-10-21/appvms_working/sys-usb/private.img) $ qvm-block attach --ro -o frontend-dev=xvdap backup-vm dom0:/dev/loop10 qvm-block: error: backend vm 'dom0' doesn't expose device 'dev/loop10' Is this the correct way to attach a vm private.img to a different vm, to take a backup? Thank you for your help! [1] https://github.com/QubesOS/qubes-issues/issues/3084 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/qubes-users/295c2632-2337-497e-b0ec-c4486676ca01%40posteo.de.
OpenPGP_signature.asc
Description: OpenPGP digital signature
