[adding some qemu folks for a side note] On 11/26/19 3:39 PM, Peter Krempa wrote:
A pull mode backup job uses temporary disk images to hold the changed parts of the disk while the client is copying the changes. Since usage of the temporary space can be monitored but doesn't really fit any of the existing stats fields introduce new fields for reporting this data.
Signed-off-by: Peter Krempa <pkrempa@redhat.com> --- include/libvirt/libvirt-domain.h | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
Nice addition. Note that in an incremental backup, the temporary file should never grow larger in size than the bitmap that is feeding it (as only the clusters represented in the bitmap have to do a copy-on-write to the temporary file) I'd still thinking about a possible tweak to qemu to make it possible to guarantee that the temporary file during an incremental pull mode cannot occupy more space than the size covered by the bitmap (right now, if the backup lasts long enough, a guest could proceed to overwrite the entire disk, and the temporary file would grow to the guest-visible size; but if I add a mode where the NBD export returns EIO for attempts to read a portion of the disk not covered by the bitmap, then only the portions covered by the bitmap need to worry about copy-on-write to the temporary file).
diff --git a/include/libvirt/libvirt-domain.h b/include/libvirt/libvirt-domain.h index 0e490254fd..b52f58aa8f 100644 --- a/include/libvirt/libvirt-domain.h +++ b/include/libvirt/libvirt-domain.h @@ -3586,6 +3586,20 @@ typedef enum { */ # define VIR_DOMAIN_JOB_SUCCESS "success"
+/** + * VIR_DOMAIN_JOB_DISK_TEMP_USED: + * virDomainGetJobStats field: current usage of temporary disk space for the + * job in bytes as VIR_TYPED_PARAM_ULLONG. + */ +# define VIR_DOMAIN_JOB_DISK_TEMP_USED "disk_temp_used" + +/** + * VIR_DOMAIN_JOB_DISK_TEMP_TOTAL: + * virDomainGetJobStats field: possible total temporary disk space for the + * job in bytes as VIR_TYPED_PARAM_ULLONG. + */ +# define VIR_DOMAIN_JOB_DISK_TEMP_TOTAL "disk_temp_total"
If I'm running an incremental backup of a 1G disk, and the bitmap says only 512M was dirty, will disk_temp_total report 512M (even though disk_temp_used can grow up to 1G, without my proposed patch to make qemu enforce the use of the temp file only to portions covered by the bitmap), or will disk_temp_total report 1G? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org