qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qcow2: online snasphots : internal vs external ?
Date: Mon, 27 Aug 2012 12:10:34 +0200	[thread overview]
Message-ID: <k1fh2q$itj$1@ger.gmane.org> (raw)
In-Reply-To: <7e7d4bb6-17ab-439b-8ec5-2e4a6a98269d@mailpro>

Il 27/08/2012 11:26, Alexandre DERUMIER ha scritto:
> how can I rollback to the point of the snapshot.
> 
> exemple :
> image1.qcow2
> file : /beforesnap1
> take a snaphot (snap1), so qemu switch to snap1.qcow2
> write some file:
> file: 
>     /aftersnap1.
>     /beforesnap1
> 
> Now, how can I rollback to the point of time of snap1 ?
> I can reuse image1.qcow2, but if I write some datas on it, I don't
> see how I can return to the point of time of the snap1. (like qemu-image -a
> with internal snapshots)

If you can drop snap1.qcow2 altogether, you just use image1.qcow2 the
next time you start QEMU.

If you cannot, you create snap2.qcow2 based on image1.qcow2:

  qemu-img -f qcow2 -obacking_file=image1.qcow2 snap2.qcow2

and use it the next time you start QEMU.

Paolo

  reply	other threads:[~2012-08-27 10:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <10f390de-14b5-45c6-8d24-202e40cc2598@mailpro>
2012-08-25 13:25 ` [Qemu-devel] qcow2: online snasphots : internal vs external ? Alexandre DERUMIER
2012-08-25 14:01   ` Stefan Hajnoczi
2012-08-25 17:06     ` Alexandre DERUMIER
2012-08-26  7:07       ` Stefan Hajnoczi
2012-08-26  9:56         ` Alexandre DERUMIER
2012-08-27  9:04           ` Stefan Hajnoczi
2012-08-27  9:26             ` Alexandre DERUMIER
2012-08-27 10:10               ` Paolo Bonzini [this message]
2012-08-27 13:12                 ` Alexandre DERUMIER
2012-08-27 10:13             ` Paolo Bonzini
2012-08-27 16:12             ` Kevin Wolf
2012-08-28  8:11               ` Stefan Hajnoczi
2012-08-28  8:22                 ` Alexandre DERUMIER

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='k1fh2q$itj$1@ger.gmane.org' \
    --to=pbonzini@redhat.com \
    --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).