From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH v2 0/5] improve logging for dirty bitmap PBS backups
Date: Wed, 19 Aug 2020 19:35:41 +0200 [thread overview]
Message-ID: <c0ecb331-bd01-dada-f55d-dd902a2a23cc@proxmox.com> (raw)
In-Reply-To: <20200819150204.9178-1-s.reiter@proxmox.com>
On 19.08.20 17:01, Stefan Reiter wrote:
> Makes the log output more useful for dirty bitmap backups and fixes some minor
> issues.
>
> A new QMP call is introduced to avoid shoving even more data in the possibly
> often called 'query-backup' and not having to do some hacky special casing for
> the first query iteration.
>
> The new QMP call is gated behind a new proxmox feature flag. The previous
> behaviour of having 'dirty' in 'query-backup' is retained for compatibility with
> older qemu-server versions.
>
>
> v2:
> * keep 'dirty' flag in query-backup
> * add patch 5
>
>
> qemu: Stefan Reiter (1):
> PVE: add query-pbs-bitmap-info QMP call
>
> monitor/hmp-cmds.c | 28 ++++++-----
> pve-backup.c | 117 ++++++++++++++++++++++++++++++++-----------
> qapi/block-core.json | 57 ++++++++++++++++++++-
> 3 files changed, 159 insertions(+), 43 deletions(-)
>
> qemu-server: Stefan Reiter (4):
> vzdump: improve logging output with dirty bitmaps
> vzdump: display actually uploaded chunks as 'write' speed
> vzdump: log 100% percent in case $target is 0
> vzdump: don't use dirty bitmap when VM was off
>
> PVE/VZDump/QemuServer.pm | 75 +++++++++++++++++++++++++++++++---------
> 1 file changed, 59 insertions(+), 16 deletions(-)
>
applied series, thanks!
prev parent reply other threads:[~2020-08-19 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 15:01 [pve-devel] " Stefan Reiter
2020-08-19 15:02 ` [pve-devel] [PATCH v2 qemu 1/5] PVE: add query-pbs-bitmap-info QMP call Stefan Reiter
2020-08-19 15:02 ` [pve-devel] [PATCH v2 qemu-server 2/5] vzdump: improve logging output with dirty bitmaps Stefan Reiter
2020-08-19 15:02 ` [pve-devel] [PATCH v2 qemu-server 3/5] vzdump: display actually uploaded chunks as 'write' speed Stefan Reiter
2020-08-19 15:02 ` [pve-devel] [PATCH v2 qemu-server 4/5] vzdump: log 100% percent in case $target is 0 Stefan Reiter
2020-08-19 15:02 ` [pve-devel] [PATCH v2 qemu-server 5/5] vzdump: don't use dirty bitmap when VM was off Stefan Reiter
2020-08-19 17:35 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0ecb331-bd01-dada-f55d-dd902a2a23cc@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.reiter@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox