xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bamvor Jian Zhang <bjzhang@suse.com>
To: xen-devel@lists.xen.org
Cc: zzhou@suse.com, ian.campbell@citrix.com, hahn@univention.de,
	ian.jackson@eu.citrix.com, cyliu@suse.com, jfehlig@suse.com,
	bjzhang@suse.com, anthony.perard@citrix.com,
	davidkiarie4@gmail.com
Subject: [RFC V5 5/5] docs: man page for xl.snapshot.cfg
Date: Mon,  7 Jul 2014 15:46:04 +0800	[thread overview]
Message-ID: <1404719164-4983-6-git-send-email-bjzhang@suse.com> (raw)
In-Reply-To: <1404719164-4983-1-git-send-email-bjzhang@suse.com>

The following content will be the file: "docs/man/xl.snapshot.conf.pod.5"

=head1 NAME

xl.snapshot.cfg - XL Domain Snapshot Configuration File Syntax

=head1 DESCRIPTION

Without the snapshot configuration file, xl snapshot-create could create
internal domain snapshot or internal disk snapshot. To create a user-defined
domain snapshot, xl requires a domain snapshot config file. It is typically
located at `/var/lib/xen/snapshots/UUID/snapshotdata-d.NAME.libxl-json` where
UUID is the uuid of domain and the NAME is the snapshot name. See
snapshot-HOWTO.txt for use cases and examples.

=head1 SYNTAX

A domain config file consists of a series of C<KEY=VALUE> pairs. It shares the
same rules with xl.cfg

=head1 OPTIONS

=over 4

=item B<name="NAME">

Specifies the name of the domain snapshot. Names of snapshots existing in one
domain must be unique. If it is not provided, it will be the epoch second from
1, Jan 1970.

=item B<description="DESCRIPTION">

Optional. The snapshot description.

=item B<creationtime="CREATIONTIME">

The creation time of this snapshot. It will be the epoch second from 1, Jan
1970. This field could not be specified by user, it will be ignored in domain
snapshot creation.

=item B<memory="MEMORY">

Describes the location of memory save image. This image is as same as the image
in "xl save". The value could be the absolute path of the memory save image or
"yes" which means `/var/lib/xen/snapshots/UUID/NAME.save`. if it is "no" or is
not provied, this snapshot will be a disk only snapshot.

=item B<type="TYPE">

Describes the domain snapshot type. The possible value are "internal",
"external". if it is not provided, this snapshot will be a internal snapshot.
Note that each disk is allowed to choice their own snapshot type which is
determined by what information is provided in DISK_SPEC_STRING

=item B<disk=[ "DISK_SPEC_STRING", "DISK_SPEC_STRING", ...]>

The disk snapshot description. See F<docs/misc/xl-disk-configuration.txt> for
rules. For internal snapshot, user should only provide vdev. For external
snapshot, user should provide vdev, format and target. Format is the format of
external snapshot file, only qcow2 is allowed at this time. Target is disk file
after the external snapshot including absolute path.

=back

      parent reply	other threads:[~2014-07-07  7:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07  7:45 [RFC V5 0/5] domain snapshot document and discussion Bamvor Jian Zhang
2014-07-07  7:46 ` [RFC V5 1/5] docs: libxl Domain Snapshot HOWTO Bamvor Jian Zhang
2014-07-07  7:46 ` [RFC V5 2/5] Libxl Domain Snapshot API Design Bamvor Jian Zhang
2014-07-11 12:47   ` Ian Campbell
2014-07-11 13:19     ` Ian Jackson
2014-07-11 15:43       ` Bamvor Jian Zhang
2014-07-14 14:42     ` Bamvor Jian Zhang
2014-07-14 15:18       ` Ian Campbell
2014-07-16  9:27         ` Bamvor Jian Zhang
2014-07-16  9:50           ` Ian Campbell
2014-07-17  8:02             ` Bamvor Jian Zhang
2014-07-07  7:46 ` [RFC V5 3/5] docs: manpage for xl snapshot command Bamvor Jian Zhang
2014-07-07  7:46 ` [RFC V5 4/5] xl snapshot-xxx implementation details Bamvor Jian Zhang
2014-07-07  7:46 ` Bamvor Jian Zhang [this message]

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=1404719164-4983-6-git-send-email-bjzhang@suse.com \
    --to=bjzhang@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=cyliu@suse.com \
    --cc=davidkiarie4@gmail.com \
    --cc=hahn@univention.de \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jfehlig@suse.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zzhou@suse.com \
    /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).