From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
jsnow@redhat.com, den@virtuozzo.com
Subject: [Qemu-devel] [PATCH RFC] external backup api
Date: Fri, 22 Jan 2016 20:07:38 +0300 [thread overview]
Message-ID: <1453482459-80179-1-git-send-email-vsementsov@virtuozzo.com> (raw)
Hi all.
This is the early begin of the series which aims to add external backup
api. This is needed to allow backup software use our dirty bitmaps.
Vmware and Parallels Cloud Server have this feature.
There is only one patch here, about querying dirty bitmap from qemu by
qmp command. It is just an updated and clipped (hmp command removed) old
my patch "[PATCH RFC v3 01/14] qmp: add query-block-dirty-bitmap".
Before writing the whole thing I'd like to discuss the details. Or, may
be there are existing plans on this topic, or may be someone already
works on it?
I see it like this:
=====
- add qmp commands for dirty-bitmap functions: create_successor, abdicate,
reclaime.
- make create-successor command transaction-able
- add query-block-dirty-bitmap qmp command
then, external backup:
qmp transaction {
external-snapshot
bitmap-create-successor
}
qmp query frozen bitmap, not acquiring aio context.
do external backup, using snapshot and bitmap
if (success backup)
qmp bitmap-abdicate
else
qmp bitmap-reclaime
qmp merge snapshot
=====
In the following patch query-bitmap acquires aio context. This must be
ofcourse dropped for frozen bitmap.
But to make it in true way, I think, I should check somehow that this is
not just frozen bitmap, but the bitmap frozen by qmp command, to avoid
incorrect quering of bitmap frozen by internal backup (or other
mechanizm).. May be, it is not necessary.
--
1.8.3.1
next reply other threads:[~2016-01-22 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 17:07 Vladimir Sementsov-Ogievskiy [this message]
2016-01-22 17:07 ` [Qemu-devel] [PATCH] qmp: add query-block-dirty-bitmap Vladimir Sementsov-Ogievskiy
2016-01-22 17:22 ` Denis V. Lunev
2016-01-22 17:28 ` Vladimir Sementsov-Ogievskiy
2016-01-22 18:28 ` Denis V. Lunev
2016-01-22 18:43 ` Eric Blake
2016-02-05 19:48 ` [Qemu-devel] [PATCH RFC] external backup api John Snow
2016-02-06 9:19 ` Vladimir Sementsov-Ogievskiy
2016-02-08 21:14 ` John Snow
2016-02-09 15:54 ` Vladimir Sementsov-Ogievskiy
2016-02-09 16:51 ` John Snow
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=1453482459-80179-1-git-send-email-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).