From: Alberto Garcia <berto@igalia.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu block <qemu-block@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] QCOW rebases on running VMs
Date: Fri, 29 Jan 2016 22:16:15 +0200 [thread overview]
Message-ID: <20160129201615.GA18614@perseus.local> (raw)
In-Reply-To: <56AA32DE.80005@redhat.com>
On Thu, Jan 28, 2016 at 08:25:18AM -0700, Eric Blake wrote:
> > 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.
The intermediate block streaming code was finished and ready to be
merged about half a year ago. Unfortunately there were conflicts with
other changes that were happening at the same time so it had to be
rolled back.
Here's the latest version of the series:
https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg05754.html
And here's a recent summary of the problems that prevent it from being
merged:
https://lists.gnu.org/archive/html/qemu-block/2015-12/msg00180.html
My plan is to continue working on it.
Berto
prev parent reply other threads:[~2016-01-29 20:17 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
2016-01-29 20:16 ` Alberto Garcia [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=20160129201615.GA18614@perseus.local \
--to=berto@igalia.com \
--cc=alex@alex.org.uk \
--cc=eblake@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 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.