From: Ian Campbell <Ian.Campbell@citrix.com>
To: Chunyan Liu <cyliu@suse.com>, Ian.Jackson@eu.citrix.com
Cc: jfehlig@suse.com, xen-devel@lists.xen.org
Subject: Re: [RFC V7 1/3] libxl domain snapshot introduction
Date: Mon, 20 Oct 2014 16:59:17 +0100 [thread overview]
Message-ID: <1413820757.29506.11.camel@citrix.com> (raw)
In-Reply-To: <1412930928-14309-2-git-send-email-cyliu@suse.com>
On Fri, 2014-10-10 at 16:48 +0800, Chunyan Liu wrote:
> Domain snapshot includes disk snapshots and domain state saving. domain
> could be resumed to the very state when the snapshot was created. This
> kind of snapshot is also referred to as a domain checkpoint or system
> checkpoint.
Are these checkpoints considered consistent?
>
> Disk snapshot is crash-consistent if the domain is running.
Did you mean inconsistent here?
> To libxl,
> even domain is paused, there is no data flush to disk operation. So, for
> active domain (domain is started), take a disk-only snapshot and then
> resume, it is as if the guest had crashed. For this reason, we only
> support disk-only snapshot when domain is inactive (like: libvirt defines
> but not start the domain.)
>
> Disk snapshot itself could be "internal" (like in qcow2 format, snapshot
> and delta are both in one image file), or "external" (snapshot in one file,
> delta in another).
>
> Expected 4 types of operations:
>
> "domain snapshot create":
> means saving domain state (if not disk-only) and doing disk snapshots.
>
> "domain snapshot revert":
> means rolling back to the state of indicated snapshot.
This operation is only possible on what you call a "checkpoint" in the
first paragraph. is the right?
>
> "domain snapshot delete":
> delete indicated domain snapshot.
>
> "domain snapshot list":
> list domain snapshot information.
next prev parent reply other threads:[~2014-10-20 15:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 8:48 [RFC V7 0/3] domain snapshot document Chunyan Liu
2014-10-10 8:48 ` [RFC V7 1/3] libxl domain snapshot introduction Chunyan Liu
2014-10-20 15:59 ` Ian Campbell [this message]
2014-10-21 3:25 ` Chun Yan Liu
2014-10-10 8:48 ` [RFC V7 2/3] libxl domain snapshot API design Chunyan Liu
2014-10-20 16:11 ` Ian Campbell
2014-10-21 4:18 ` Chun Yan Liu
2014-10-22 3:59 ` Chun Yan Liu
2014-10-29 10:26 ` Ian Campbell
2014-11-03 7:37 ` Chun Yan Liu
2014-10-10 8:48 ` [RFC V7 3/3] xl snapshot-xxx Design Chunyan Liu
2014-10-20 16:39 ` Ian Campbell
2014-10-21 5:37 ` Chun Yan Liu
2014-10-22 4:10 ` Chun Yan Liu
2014-10-29 8:32 ` Chun Yan Liu
2014-10-29 10:19 ` Ian Campbell
2014-10-29 8:34 ` Chun Yan Liu
2014-10-29 10:22 ` Ian Campbell
2014-10-17 6:04 ` [RFC V7 0/3] domain snapshot document Chun Yan Liu
2014-10-17 9:50 ` Ian Campbell
2014-10-20 16:12 ` Ian Campbell
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=1413820757.29506.11.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=cyliu@suse.com \
--cc=jfehlig@suse.com \
--cc=xen-devel@lists.xen.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.