From: Eric Blake <eblake@redhat.com>
To: Kuniyasu Suzaki <k.suzaki@aist.go.jp>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] live migration which includes previos snapshot
Date: Fri, 02 Nov 2012 09:41:28 -0600 [thread overview]
Message-ID: <5093E9A8.4090801@redhat.com> (raw)
In-Reply-To: <20121103.001805.37445977.k.suzaki@aist.go.jp>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On 11/02/2012 09:18 AM, Kuniyasu Suzaki wrote:
>> 1. Make the original image read-only accessible over NFS.
>> 2. Modify QEMU to create two external snapshot files when the VM is
>> paused for migration (during your fork operation):
>>
>> /host-a/original.qcow2
>> /host-a/new.qcow2 (backing file: /host-a/original.qcow2)
>> /host-b/new.qcow2 (backing file: /host-b/original.qcow2)
>>
>> 3. After fork the two VMs will write into their respective new.qcow2
>> files. original.qcow2 is never modified anymore.
>
> Does it means nested qcow2?
> Does it allow to use a snapshot image in original.qcow2?
> # I want to share a snapshot image taken by "savevm" on two QEMUs.
This is not yet possible, someone has to step up and write patches to
make it possible.
--
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 --]
prev parent reply other threads:[~2012-11-02 15:41 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
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 [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=5093E9A8.4090801@redhat.com \
--to=eblake@redhat.com \
--cc=k.suzaki@aist.go.jp \
--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 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.