From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"aliguori@us.ibm.com" <aliguori@us.ibm.com>,
"stefanha@gmail.com" <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"blauwirbel@gmail.com" <blauwirbel@gmail.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] live backup vm
Date: Wed, 12 Dec 2012 10:16:06 +0800 [thread overview]
Message-ID: <50C7E8E6.3060802@linux.vnet.ibm.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F7557871C7B@lisa.maurer-it.com>
OK, I'll adjust the code into the upstream framework, thanks for your
declaration.
> OK, I will try to give a short overview on the functionality.
>
> First, we decided to use 'internal' snapshots for our 'live snapshot' implementation.
> Internal snapshots almost always use some kind of reference counting, making
> snapshot action (like 'create/delete snapshot') quite efficient and fast.
>
> Internal snapshot totally depends on the storage backend. For now we can create
> internal snapshots on the following storage backend:
>
> * qcow2 files
> * rbd
> * sheepdog
> * nexenta iscsi
>
> As you can see, creating internal snapshots sometimes needs external tool. For example we use the
> nexenta API to create snapshots, while we use libiscsi to access them inside qemu.
>
> So our snapshot implementation uses the following steps:
>
> 1.) qmp: savevm-start [statefile]
>
> This save the VM state into [statefile] and then stops the VM.
>
> 2.) qga freezefs
>
> 3.) create snapshots: either using external tools or by qmp: snapshot-drive
>
> 4.) gqa unfreezefs
>
> 5.) qmp: savevm-end
>
> This restarts/resumes the VM
>
>> Have some questions:
>> in qmp_savevm_start(), vm_stop(RUN_STATE_SAVE_VM), I think this will
>> stop the VM running make it not lively, am I right?
>
> Yes, we need to halt the VM for a short period of time while we make
> snapshots. But that time is usually short.
>
> - Dietmar
>
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2012-12-12 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 8:24 [Qemu-devel] [RFC PATCH 0/2] live backup vm Wenchao Xia
2012-12-07 10:12 ` Dietmar Maurer
2012-12-09 4:37 ` Wenchao Xia
2012-12-09 7:12 ` Dietmar Maurer
2012-12-10 1:37 ` Wenchao Xia
2012-12-10 6:23 ` Dietmar Maurer
2012-12-11 7:14 ` Wenchao Xia
2012-12-11 7:46 ` Dietmar Maurer
2012-12-12 2:16 ` Wenchao Xia [this message]
2012-12-12 8:30 ` Paolo Bonzini
2012-12-12 8:50 ` Dietmar Maurer
2012-12-12 9:03 ` Dietmar Maurer
2012-12-12 10:00 ` Paolo Bonzini
2012-12-08 8:24 ` [Qemu-devel] [RFC PATCH 1/2] live backup vm, export functions Wenchao Xia
2012-12-08 8:24 ` [Qemu-devel] [RFC PATCH 2/2] live backup vm, snapshots all lively Wenchao Xia
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=50C7E8E6.3060802@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=dietmar@proxmox.com \
--cc=kwolf@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 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.