On Fri, Mar 14, 2025 at 14:18:03 -, Michael Niehren wrote:
> one more ...
>
> what would happen, if i create the qcow2 image with zstd compression enabled
> and
> use the '--reuse-external' flag ?
> Would qemu write compressed data in it or not ?
It would not be compressed, as I've explained
ok, so only setting the compression type to zstd in the backupxml would be
possible from libvirt, right ?
An implementation only in the backup job would be great, that would fit my
needs.
Maybe some more flags in the backupxml file would be useful. I used for
compressing
on the zstd call
"--sparse --rsyncable -B128 "
as the files are later transfered with rsync. The compression level would also
b
On Fri, Mar 14, 2025 at 13:11:00 +0100, Peter Krempa wrote:
> On Fri, Mar 14, 2025 at 11:12:09 -, Michael Niehren wrote:
[...]
> As noted above the fact that any compression algorithm is enabled
> doesn't mean that compressed data will be written.
>
> I don't see us ever wanting to enable co
On Fri, Mar 14, 2025 at 11:12:09 -, Michael Niehren wrote:
> Hi,
>
> currently i use on all VM's qcow2-Images with zlib compression. If i do an
> Backup, the Backup-Image will
> be compressed with zstd Level 3 to shrink the image for transfering it over
> not so fast internet connections.
L
Hi,
currently i use on all VM's qcow2-Images with zlib compression. If i do an
Backup, the Backup-Image will
be compressed with zstd Level 3 to shrink the image for transfering it over not
so fast internet connections.
So, why not directly using zstd compression on the images. Are there any
re
