xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David kiarie <davidkiarie4@gmail.com>
To: Bamvor Jian Zhang <bjzhang@suse.com>
Cc: Zhiqiang Zhou <ZZhou@suse.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Chun Yan Liu <CYLiu@suse.com>,
	xen-devel@lists.xen.org, Jim Fehlig <JFEHLIG@suse.com>,
	Anthony PERARD <Anthony.perard@citrix.com>
Subject: Re: [RFC v3] domain snapshot documents
Date: Fri, 16 May 2014 18:07:45 +0300	[thread overview]
Message-ID: <CABdVeACP0dyCAFbHABw1W1PCv0exqbTi_Ftfi5oVuoygsmrsyw@mail.gmail.com> (raw)
In-Reply-To: <5376989B0200003000034D12@soto.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 2252 bytes --]

On Fri, May 16, 2014 at 6:00 PM, Bamvor Jian Zhang <bjzhang@suse.com> wrote:

> Hi, david
>
> > On Thu, May 15, 2014 at 4:58 PM, Bamvor Jian Zhang <bjzhang@suse.com>
> wrote:
> >
> > > Hi,
> > >
> > > here is the third version about domain snapshot documents, the second
> > > version
> > > and the first version is here[1][2].
> ...
> > > 2, new functions
> > > there is no common api like libxl_snapshot_xxx. the reason is that
> > > different
> > > toolstack may need to different event handling machanism(synchronize or
> > > asynchronize). and obviously, domain snapshot create need async
> handler.
> > > so i
> > > decide to only provide the sub api for xl and other toolstack(e.g.
> > > libvirt).
> > > it make eailer for toolstack to handle the event by themselves.
> > >
> > > 1), in libxl/libxl.h
> > > the implementation will be located in libxl_snapshot.c
> > > /* disk snapshot api
> > >  * support create for external and internal disks, support delete for
> > > internal
> > >  * snapshot of disks.
> > >  */
> > > /* create disk snapshot according to the device name in snapshot
> array. nb
> > > is
> > >  * the number of snapshot array.
> > >  * use the qmp transaction to ensure all snapshot of disk is coherence.
> > >  */
> > > int libxl_disk_snapshot_create(libxl_ctx *ctx, int domid,
> > >                                libxl_disk_snapshot *snapshot, int nb,
> > >                                const libxl_asyncop_how *ao_how);
> > > /* delete number of nb disk snapshot describe in snapshot array
> > >  */
> > > int libxl_disk_snapshot_delete(libxl_ctx *ctx, int domid,
> > >                                libxl_disk_snapshot *snapshot, int nb);
>
Are this the only two functions you are exposing?I mean the API?or am I
getting something wrong?

>
>
> >
> > >
> > I think we also need revert libxl_disk_snapshot_revert() here.
> there are two methods for revert disk snapshot state in qemu: call
> "loadvm" hmp
> and "qemu-img snapshot -a". and i will call loadvm for reverting the qemu
> state
> and disk state in libxl_snapshot_create.
> user could revert the dedicate disk snapshot with qemu-img when domain is
> not
> running.it seems not a good idea wrap the qemu-img command in libxl.
>
> regards
>
> bamvor
>
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 3555 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-05-16 15:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 13:58 [RFC v3] domain snapshot documents Bamvor Jian Zhang
2014-05-15 15:24 ` Philipp Hahn
2014-05-16  7:21   ` Bamvor Jian Zhang
2014-05-16 10:36 ` David kiarie
2014-05-16 15:00   ` Bamvor Jian Zhang
2014-05-16 15:07     ` David kiarie [this message]
2014-05-19  3:45       ` Bamvor Jian Zhang
2014-05-19  5:34         ` David kiarie
2014-06-05 22:44         ` Jim Fehlig
2014-06-07  5:20           ` David kiarie
2014-06-08  3:05           ` Bamvor Jian Zhang
     [not found] <5375388A0200003000034775@suse.com>
2014-06-05 22:41 ` Jim Fehlig
2014-06-09 14:08   ` Bamvor Jian Zhang
2014-06-16  6:21     ` David kiarie
2014-06-16  6:51       ` David kiarie

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=CABdVeACP0dyCAFbHABw1W1PCv0exqbTi_Ftfi5oVuoygsmrsyw@mail.gmail.com \
    --to=davidkiarie4@gmail.com \
    --cc=Anthony.perard@citrix.com \
    --cc=CYLiu@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JFEHLIG@suse.com \
    --cc=ZZhou@suse.com \
    --cc=bjzhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).