Hi, as outlined above the behavior is still wrong. The patch suggested in [1] will fix the behavior of libvirt to what it was meant to be when preallocation=falloc was added.
But now virt-manager comes into play, the XML sent by virt-manager is exactly matching the definition of the use case to use falloc. So virt-manager triggered storage request will continue to use falloc despite libvirt being "fixed to how it was intended". The question now is should we consider changing the XML virt-manager submits so that we are back at the much faster preallocation=metadata mode? [1]: https://www.redhat.com/archives/libvir- list/2020-September/msg00105.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting To manage notifications about this bug go to: https://bugs.launchpad.net/virt-manager/+bug/1847105/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
