From: Eric Blake <eblake@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: libvir-list@redhat.com, Tim Cusack <thagrasshoppa@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [libvirt] Question regarding Snapshots
Date: Mon, 27 Feb 2017 13:37:44 -0600 [thread overview]
Message-ID: <3e3033ab-9cc9-8673-f13c-2dd658677fc9@redhat.com> (raw)
In-Reply-To: <20170227131757.vkf6twqdkzbwnsqc@eukaryote>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On 02/27/2017 07:17 AM, Kashyap Chamarthy wrote:
> On Mon, Feb 27, 2017 at 01:33:56PM +0100, Kashyap Chamarthy wrote:
>
> [...]
>
>>>> Can you make a snapshot, then go back to the base and ignore that snapshot
>>>> like a closed branch, make another snapshot, and then go back and forth
>>>> from each to each?
Yes. Or graphically, you can have:
-- A ... B ... C
/
base <
\
-- D ... E ... F
and toggle between any of the named snapshots at will. As Kashyap and
others pointed out, libvirt support for reverting to a particular
external snapshot is not fully present, so there are some manual steps
involved, but the task is still doable.
>
>> For the long answer to the complications involved in reverting to
>> external snapshots, refer this (long read):
>>
>> https://wiki.libvirt.org/page/I_created_an_external_snapshot,_but_libvirt_will_not_let_me_delete_or_revert_to_it
>
> [...]
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2017-02-27 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 21:06 [Qemu-devel] Question regarding Snapshots Tim Cusack
2017-02-27 11:01 ` Stefan Hajnoczi
2017-02-27 12:33 ` Kashyap Chamarthy
2017-02-27 13:17 ` [Qemu-devel] [libvirt] " Kashyap Chamarthy
2017-02-27 19:37 ` Eric Blake [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=3e3033ab-9cc9-8673-f13c-2dd658677fc9@redhat.com \
--to=eblake@redhat.com \
--cc=kchamart@redhat.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thagrasshoppa@gmail.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).