On Sun, Jul 12, 2020 at 07:31:30PM -0000, Tom Seewald wrote: > For example with virtualization I'd think that the changes would need > to happen around the level of libvirt, and not to specific a front-end > like GNOME boxes or virt-manager. It's also probably not sufficient to > just set nodatacow on the default VM image directory as users may use > a non-default directory for qcow2 images. Hence I don't think these > issues will always have trivial solutions. The next release of libvirt (due in rawhide in ~1 week time) has improved btrfs support. It will default to always setting "nocow" for any libvirt storage pool that is created on a btrfs filesystem, with option to override if desired. This should make GNOME Boxes, virt-manager, virt-install and cockpit all "do the right thing" out of the box in most circumstances. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ 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
