qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	qemu-devel@nongnu.org, Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Image Streaming API
Date: Mon, 29 Aug 2011 14:16:44 -0500	[thread overview]
Message-ID: <4E5BE59C.9040000@us.ibm.com> (raw)
In-Reply-To: <1314104305-20523-1-git-send-email-stefanha@linux.vnet.ibm.com>

On 08/23/2011 07:58 AM, Stefan Hajnoczi wrote:
> These patches put in place the image streaming QMP/HMP commands and
> documentation.  Image streaming itself is not implemented by this patch series
> but the HMP/QMP commands that libvirt uses are implemented to return
> NotSupported.
>
> The Image Streaming API can be used to copy the contents of a backing file into
> the image file while the guest is running.  The API is described on the wiki:
> http://wiki.qemu.org/Features/LiveBlockMigration/ImageStreamingAPI
>
> The point of this series is to commit QEMU to the API that we have worked out
> with libvirt.  The QED Image Streaming series that I posted earlier provides an
> implementation for the QED image format only.  I am currently working on a
> generic block layer implementation so that any format with backing file support
> can do image streaming.
>
> For reference, the QED-specific implementation lives here:
> http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/stream-command

Luiz, can you bring this in through your tree with an Ack from Kevin.

Regards,

Anthony Liguori

>
> Stefan Hajnoczi (4):
>    qmp: add block_stream command
>    qmp: add block_job_set_speed command
>    qmp: add block_job_cancel command
>    qmp: add query-block-jobs
>
>   blockdev.c      |   55 ++++++++++++++++++
>   blockdev.h      |    6 ++
>   hmp-commands.hx |   44 ++++++++++++++
>   monitor.c       |   19 ++++++
>   monitor.h       |    1 +
>   qerror.h        |    3 +
>   qmp-commands.hx |  172 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>   7 files changed, 300 insertions(+), 0 deletions(-)
>

  parent reply	other threads:[~2011-08-29 19:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 12:58 [Qemu-devel] [PATCH 0/4] Image Streaming API Stefan Hajnoczi
2011-08-23 12:58 ` [Qemu-devel] [PATCH 1/4] qmp: add block_stream command Stefan Hajnoczi
2011-08-23 16:33   ` Adam Litke
2011-08-30  9:43     ` Stefan Hajnoczi
2011-08-23 12:58 ` [Qemu-devel] [PATCH 2/4] qmp: add block_job_set_speed command Stefan Hajnoczi
2011-08-23 12:58 ` [Qemu-devel] [PATCH 3/4] qmp: add block_job_cancel command Stefan Hajnoczi
2011-08-23 12:58 ` [Qemu-devel] [PATCH 4/4] qmp: add query-block-jobs Stefan Hajnoczi
2011-08-23 16:28   ` Adam Litke
2011-08-29 19:16 ` Anthony Liguori [this message]
2011-08-29 19:45   ` [Qemu-devel] [PATCH 0/4] Image Streaming API Luiz Capitulino
2011-08-30  3:19 ` Zhi Yong Wu
2011-08-30  9:28   ` Stefan Hajnoczi
2011-08-30 13:32     ` Adam Litke

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=4E5BE59C.9040000@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=agl@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).