From: Eric Blake <eblake@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: Alberto Garcia <berto@igalia.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] QCOW rebases on running VMs
Date: Thu, 28 Jan 2016 08:25:18 -0700 [thread overview]
Message-ID: <56AA32DE.80005@redhat.com> (raw)
In-Reply-To: <AD328CF0-9F95-4C64-84F1-32DCF1413A0F@alex.org.uk>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On 01/28/2016 05:36 AM, Alex Bligh wrote:
>
> On 27 Jan 2016, at 20:47, Eric Blake <eblake@redhat.com> wrote:
>
>>>
>>>
>>> If not, do I need to use QMP magic instead?
>>
>> Yes. block-commit is your friend.
>
> Sadly what I need is block-stream to an intermediate layer (as I
> want to merge in the other direction); I don't think that proposal
> was ever implemented.
>
> http://wiki.qemu.org/Features/Snapshots#Streaming_to_an_Intermediate_Layer_.5Bproposal.5D
Alberto was working on it last; this was the most recent mail I found on
the topic (just to the qemu-block list):
https://lists.gnu.org/archive/html/qemu-block/2015-12/msg00214.html
so although I recall some RFC patches having been posted, you are right
that it still needs some work to be merged in.
--
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:[~2016-01-28 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 18:04 [Qemu-devel] QCOW rebases on running VMs Alex Bligh
2016-01-27 19:01 ` Max Reitz
2016-01-27 20:47 ` Eric Blake
2016-01-28 12:36 ` Alex Bligh
2016-01-28 15:25 ` Eric Blake [this message]
2016-01-29 20:16 ` Alberto Garcia
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=56AA32DE.80005@redhat.com \
--to=eblake@redhat.com \
--cc=alex@alex.org.uk \
--cc=berto@igalia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.