All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bamvor Jian Zhang" <bjzhang@suse.com>
To: xen-devel@lists.xen.org
Cc: Anthony.perard@citrix.com,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: [RFC] about libxl snapshot
Date: Thu, 03 Apr 2014 00:49:13 -0600	[thread overview]
Message-ID: <533D74E90200003000029A3E@soto.provo.novell.com> (raw)

Hi, 

i have sent a patch about implement disk internal snapshot. this is our first
step about snapshot.

our plan about snapshot is:
1, basic disk snapshot support(internal snapshot, qdisk as backend).
ALREADY SENT.
2, vm snapshot(memory save, snapshot the whole snapshot with transaction qmp
opeartion, only support internal disk snapshot at this step.
in this step, we plan to add the vm snapshot record in xenstore in domain in
order to management the status of vm snapshot.

question:
in GSOC2013, there is a requirement: "Add VM snapshot functionalities to libxl
save/restore and migration functions". is it mean add a flag to create snapshot
in save, revert snapshot in restore besides the dedicated vm snapshot command?
or just implement the snapshot in save, restore and migration?
it might be more clear for user if there is a dedicated snapshot command.

3, some "advanced" feature such driver-mirror, support other backend.

when i prepare to send this out, i found that there is a GSOC project during
community review this week. i am sorry about i do not send this discussion
eariler. sorry if i break the plan of xen community.

regards

bamvor

             reply	other threads:[~2014-04-03  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  6:49 Bamvor Jian Zhang [this message]
2014-04-03 14:26 ` [RFC] about libxl snapshot Ian Jackson
2014-04-07  7:43   ` Bamvor Jian Zhang

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=533D74E90200003000029A3E@soto.provo.novell.com \
    --to=bjzhang@suse.com \
    --cc=Anthony.perard@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.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.