From: Ian Campbell <Ian.Campbell@citrix.com>
To: Chun Yan Liu <cyliu@suse.com>
Cc: Jim Fehlig <JFEHLIG@suse.com>,
Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [RFC V7 2/3] libxl domain snapshot API design
Date: Wed, 29 Oct 2014 10:26:49 +0000 [thread overview]
Message-ID: <1414578409.29975.9.camel@citrix.com> (raw)
In-Reply-To: <54479C3302000066000712E6@soto.provo.novell.com>
On Tue, 2014-10-21 at 21:59 -0600, Chun Yan Liu wrote:
> > Is this operation any different to destroying the domain and using
> > libxl_domain_restore to start a new domain based on the snapshot? Is
> > this operation just a convenience layer over that operation?
>
> It depends on implementation. It's a simple way to destroy the domain
> first, then start new domain based on snapshot. But destroying the
> domain may be not good to user (after xl snapshot-revert, domid is
> changed.) and may cause some problem in libvirt (may affect its
> event handling ?).
I would hope that as part of the implementation libvirt would learn to
cope with this if it can't already, but it can surely already cope with
migration and reverting to a snapshot is not so very different.
> Or another way is: not destroying the domain, but through a process
> like pause domain, reload memory, reload disk snapshot, reload config
> file, resume domain. Complex but maybe better.
I don't think the complexity of resetting an already existing domain's
memory and i/o state to an earlier incarnation rather than starting from
a clean slate should be underestimated either (TBH it never occurred to
me that you might try this). AFAICT you'd need to effectively tear
everything down to a blank slate and then do all the same things that
you would do in the destroy case.
Ian.
next prev parent reply other threads:[~2014-10-29 10:26 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
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 [this message]
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=1414578409.29975.9.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JFEHLIG@suse.com \
--cc=cyliu@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.