[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC V8 2/3] libxl domain snapshot API design

On Mon, Nov 10, 2014 at 8:17 AM, Chunyan Liu <cyliu@xxxxxxxx> wrote:

> 3. Function Implementation
>    libxl_domain_snapshot_create:
>        1). check args validation
>        2). save domain memory through save-domain
>        3). take disk snapshot by qmp command (if domian is active) or qemu-img
>            command (if domain is inactive).

By "active" here, do you you mean "live" (vs paused)?

>    libxl_domain_snapshot_delete:
>        1). check args validation
>        2). remove memory state file.
>        3). delete disk snapshot. (for internal disk snapshot, through qmp
>            command or qemu-img command)

Out of curiosity, why is this necessary?  Is libxl keeping track of
the snapshots somewhere?  Or qemu?

Or to put it a different way, since the caller knows the filenames,
why can't the caller just erase the files themselves?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.