From: Philipp Hahn <hahn@univention.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Correct syntax for named snapshots
Date: Thu, 27 Oct 2011 10:24:40 +0200 [thread overview]
Message-ID: <201110271024.46694.hahn@univention.de> (raw)
In-Reply-To: <CAEJNuHxWFz_xJy+mhUVaGmkcSs83ZV3JptmEJbYcGQmg39b3UQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
Hello Ottaavio,
On Wednesday 26 October 2011 18:24:01 Ottavio wrote:
> According to the latest doc file you create a named snapshot like this:
>
> qemu-img snapshot [-l | -a snapshot | -c snapshot | -d snapshot]
> base-image.img
>
> Is this other following syntax still supported or deprecated:
>
> "qemu-img create -f qcow2 -b base-image.img snapshot.img" ?
These are two different things:
The first one creates an *internal* snapshot, which is stored internally in a
*single* qcow2 file.
The second one creates an *external* snapshot, which creates a *new second*
qcow2 file.
The first functionality requires a lot more work for qcow2, which can easily
corrupt your qcow2 file if something goes wrong. Because of this QED (one
follow-up format of Qcow) IMHO dropped support for internal snapshots.
The second variante has the drawback, that for each snapshot your get an
additional file, which your have to manage. Deleting one file from the middle
of such a chain breaks all following snapshots, so be careful when you do
delete files.
And yes, both are still supported.
Sincerely
Philipp
--
Philipp Hahn Open Source Software Engineer hahn@univention.de
Univention GmbH Linux for Your Business fon: +49 421 22 232- 0
Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99
http://www.univention.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2011-10-27 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 16:24 [Qemu-devel] Correct syntax for named snapshots Ottavio
2011-10-27 7:29 ` Stefan Hajnoczi
2011-10-27 8:24 ` Philipp Hahn [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=201110271024.46694.hahn@univention.de \
--to=hahn@univention.de \
--cc=qemu-devel@nongnu.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).