On Sun, Apr 4, 2021 at 5:40 AM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > > On Sat, Apr 3, 2021 at 11:40 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> >> On Sat, Apr 3, 2021 at 10:42 AM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: >> > >> > Before I submit a BZ I figured maybe some discussion was in order. >> > >> > As the default fs is now btrfs and it's well known to be bad for VMs, I'm surprised this wasn't already implemented. >> > >> >> It is implemented. >> https://listman.redhat.com/archives/libvir-list/2020-July/msg01377.html >> >> Applies to virt-install, virt-manager, GNOME Boxes, and Cockpit. >> >> If you do a clean install and haven't setup a storage pool yet before >> copying over VM images from some other source, they won't be nodatacow >> because the enclosing directory isn't yet nodatacow. > > > Ahh.. That's good at least. I have a fresh system install but using an existing /home so I had to do it manually. Yeah nodatacow is set when the pool is created. So if it was created before the patch was added to Fedora 33, around July 2020, it wouldn't be set automatically later. > It should be possible, however, to mark the images folder +C even if it wouldn't affect existing images. It is. -- 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
