On 05/11/2017 09:56 AM, Eric Blake wrote: > > On IRC, John, Kevin, and I were discussing the current situation with > libvirt NBD storage migration. When libvirt creates a file on the > destination (rather than the user pre-creating it), it currently > defaults to 0.10 [v2] images, even if the source was a 1.1 image [v3] > (arguably something that could be improved in libvirt, but > https://bugzilla.redhat.com/show_bug.cgi?id=1371749 was closed as not a > bug). > > Therefore, the use case of doing a mirror job to a v2 image, and having > that image become thick even though the source was thin, is happening > more than we'd like > (https://bugzilla.redhat.com/show_bug.cgi?id=1371749). While Kevin had
Bah, pasted the wrong link. Correct one is: https://bugzilla.redhat.com/show_bug.cgi?id=1219541 -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
