On Thu, Jul 11, 2019 at 03:29:35PM +0200, Max Reitz wrote: > When preallocating an encrypted qcow2 image, it just lets the protocol > driver write data and then does not mark the clusters as zero. > Therefore, reading this image will yield effectively random data. > > As such, we have not fulfilled the promise of always writing zeroes when > preallocating an image in a while. It seems that nobody has really > cared, so change the documentation to conform to qemu's actual behavior. > > Signed-off-by: Max Reitz <mre...@redhat.com> > --- > qapi/block-core.json | 9 +++++---- > docs/qemu-block-drivers.texi | 4 ++-- > qemu-img.texi | 4 ++-- > 3 files changed, 9 insertions(+), 8 deletions(-)
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com> 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 :|
