qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] live migration which includes previos snapshot
Date: Fri, 02 Nov 2012 07:12:21 -0600	[thread overview]
Message-ID: <5093C6B5.7070901@redhat.com> (raw)
In-Reply-To: <CAJSP0QUD=_2ds_MP2_fw=y6PzFUPFDfYEH0CvTuv83too94RoA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

On 11/02/2012 04:30 AM, Stefan Hajnoczi wrote:

> II. If you want to use internal snapshots in a single qcow2 file, you
> will need to modify QEMU code more:
> 1. Implement BlockDriverState snapshot slave support so a qcow2
> snapshot can be read-only accessed as a BlockDriverState while the
> master BlockDriverState for the image still writes into the image
> file.  This is mainly qcow2 refactoring and block.c glue code.

You are not the first to request this - libvirt would also like the
ability to have read-only access into the contents of an internal
snapshot while the rest of qemu continues to write into the image.

> 2. Use Paolo's runtime NBD server to export the snapshot slave when
> the VM is forked:

An NBD server on top of the read-only state is an additional step that
will make access easier.

-- 
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: 617 bytes --]

  reply	other threads:[~2012-11-02 13:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02  3:15 [Qemu-devel] live migration which includes previos snapshot Kuniyasu Suzaki
2012-11-02  7:19 ` Stefan Hajnoczi
2012-11-02  8:24   ` Kuniyasu Suzaki
2012-11-02 10:30     ` Stefan Hajnoczi
2012-11-02 13:12       ` Eric Blake [this message]
2012-11-02 15:00         ` Kuniyasu Suzaki
2012-11-02 15:40           ` Eric Blake
2012-11-02 15:18       ` Kuniyasu Suzaki
2012-11-02 15:41         ` Eric Blake

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=5093C6B5.7070901@redhat.com \
    --to=eblake@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).