From: Eric Blake <eblake@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: Re: [Qemu-devel] Making QMP 'block-job-cancel' transactionable
Date: Tue, 28 Mar 2017 09:49:40 -0500 [thread overview]
Message-ID: <6fb77120-dcab-042f-bb51-20ccbaa38354@redhat.com> (raw)
In-Reply-To: <20170324123458.yk3rj3g47e5xr33i@eukaryote>
[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]
On 03/24/2017 07:34 AM, Kashyap Chamarthy wrote:
> While debugging some other issue, I happened to stumble across an old
> libvirt commit[*] that adds support for pivot (whether QEMU should
> switch to a target copy or not) operation as a result of issuing QMP
> 'block-job-cancel' to a 'drive-mirror' (in libvirt parlance, "block
> copy").
>
> In the libvirt commit message[*] Eric Blake writes:
>
> "[...] There may be potential improvements to the snapshot code to
> exploit block copy over multiple disks all at one point in time.
> And, if 'block-job-cancel' were made part of 'transaction', you
> could copy multiple disks at the same point in time without pausing
> the domain. [...]"
>
> I realize that 'block-job-cancel' is currently not part of the
> @TransactionAction. Is it worthwhile to do so?
Yes, it is still worthwhile to make that improvement, although it is now
2.10 material.
>
> Given the current behavior of QMP 'drive-mirror':
>
> - Upon 'block-job-complete', synchronization will end, and live QEMU
> pivots to the target (i.e. the copy)
>
> - Upon 'block-job-cancel', a point-in-time (at the time of cancel)
> copy gets created, and live QEMU will _not_ pivot.
>
> I realize that it is not possible to perform a "block copy" of multiple
> disks at the same point in time without pausing QEMU. From a brief chat
> with Stefan Hajnoczi on IRC, he does confirm that there's no current API
> for doing it atomically across multiple disks.
>
> Since Stefan asked if a bug exists for adding 'transaction' support to
> 'block-job-cancel', thought I might bring it up here first.
>
>
> [*] https://libvirt.org/git/?p=libvirt.git;a=commit;h=eaba79d --
> blockjob: support pivot operation on cancel
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-03-28 14:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 12:34 [Qemu-devel] Making QMP 'block-job-cancel' transactionable Kashyap Chamarthy
2017-03-28 14:49 ` Eric Blake [this message]
2017-03-28 15:29 ` Kashyap Chamarthy
2017-04-03 14:38 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-04-03 20:29 ` John Snow
2017-04-03 20:38 ` Eric Blake
2017-04-04 13:28 ` Kashyap Chamarthy
2017-04-04 13:54 ` Eric Blake
2017-04-11 9:42 ` Markus Armbruster
2017-04-11 10:30 ` Kashyap Chamarthy
2017-04-11 12:05 ` Kevin Wolf
2017-04-11 13:14 ` Eric Blake
2017-04-11 13:30 ` Kevin Wolf
2017-04-12 8:42 ` Fam Zheng
2017-04-12 8:59 ` Kevin Wolf
2017-04-12 9:12 ` Fam Zheng
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=6fb77120-dcab-042f-bb51-20ccbaa38354@redhat.com \
--to=eblake@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-block@nongnu.org \
--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).