On Mon, Apr 5, 2021 at 12:12 PM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > > On Mon, Apr 5, 2021 at 11:43 AM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> >> >> >> On Mon, Apr 5, 2021, 6:28 AM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: >>> >>> On Sun, Apr 4, 2021 at 5:19 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >>>> >>>> On Sun, Apr 4, 2021 at 5:40 AM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: >>>> >>>> > It should be possible, however, to mark the images folder +C even if it wouldn't affect existing images. >>>> >>>> It is. >>> >>> >>> What I meant, is that it could be marked +C even for existing installs so at least future VMs would be set correctly. >> >> >> >> The nodatacow attribute/flag is set at the time the storage pool is created. I'm not sure what would be involved in checking it every time. There's an opt out mechanism in libvirt (keep it cow). > > > Ahh, I was speaking more to the ~/.local/share/gnome-boxes/images folder. It's the same mechanism for virt-install, Cockpit, GNOME Boxes, and virt-manager. Maybe anything libvirt, because when I cleaned up a pool (virsh pool-destroy; virsh pool-undefine) and 'chattr -C /path/' and then recreated the pool with virsh, nodatacow was set again. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
