From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu 1/4] PVE: add query-pbs-bitmap-info QMP call
Date: Wed, 19 Aug 2020 11:41:30 +0200 [thread overview]
Message-ID: <8eb1f6b6-311c-5c33-237b-0601889b4f3d@proxmox.com> (raw)
In-Reply-To: <20200813120334.20928-2-s.reiter@proxmox.com>
On 13.08.20 14:03, Stefan Reiter wrote:
> Returns advanced information about dirty bitmaps used (or not used) for
> the latest PBS backup.
>
removing the "dirty" field breaks reporting in older qemu-server versions, I'd
would like to avoid that if it isn't to big of a hassle..
next prev parent reply other threads:[~2020-08-19 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 12:03 [pve-devel] [PATCH 0/4] improve logging for dirty bitmap PBS backups Stefan Reiter
2020-08-13 12:03 ` [pve-devel] [PATCH qemu 1/4] PVE: add query-pbs-bitmap-info QMP call Stefan Reiter
2020-08-19 9:41 ` Thomas Lamprecht [this message]
2020-08-13 12:03 ` [pve-devel] [PATCH qemu-server 2/4] vzdump: improve logging output with dirty bitmaps Stefan Reiter
2020-08-13 12:03 ` [pve-devel] [PATCH qemu-server 3/4] vzdump: display actually uploaded chunks as 'write' speed Stefan Reiter
2020-08-13 12:03 ` [pve-devel] [PATCH qemu-server 4/4] vzdump: log 100% percent in case $target is 0 Stefan Reiter
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=8eb1f6b6-311c-5c33-237b-0601889b4f3d@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