All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1184089 <1184089@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1184089] [NEW] [Feature request] loadvm snapshot as read-only
Date: Mon, 27 May 2013 14:55:13 +0200	[thread overview]
Message-ID: <20130527125513.GF23204@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130525082911.27253.67454.malonedeb@gac.canonical.com>

On Sat, May 25, 2013 at 08:29:11AM -0000, Michael Coppola wrote:
> There are many ways to take and manage snapshots in QEMU, but one main
> feature that's missing is the ability to 'loadvm' a LIVE snapshot and
> have all future changes redirected to a temporary file.  This would
> effectively be combining the -loadvm and -snapshot switches and make the
> snapshot read-only.  With this feature, users would be provided a
> "sandbox" and be able to start and restart the same live snapshot
> without corrupting the image in doing so.

This should be possible soon.  Wenchao Xia is working on new monitor
commands that allow you to combine internal snapshots (loadvm/savevm)
with external snapshots (blockdev-snapshot-sync).

You would submit a QMP 'transaction' command that specifies a loadvm
followed by a blockdev-snapshot-sync.  This operation is atomic.

Note that internal snapshots do not destroy the snapshot.  Therefore,
when you loadvm an internal snapshot and write to the disk, you are not
modifying the internal snapshot only the current state of the disk.  You
can loadvm it again later.

Stefan

  reply	other threads:[~2013-05-27 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  8:29 [Qemu-devel] [Bug 1184089] [NEW] [Feature request] loadvm snapshot as read-only Michael Coppola
2013-05-27 12:55 ` Stefan Hajnoczi [this message]
2013-05-27 22:42 ` [Qemu-devel] [Bug 1184089] " Michael Coppola
2013-05-28  8:22   ` Stefan Hajnoczi
2017-04-27 15:33 ` Thomas Huth
2021-04-22  3:56 ` Thomas Huth
2021-06-21  4:17 ` Launchpad Bug Tracker

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=20130527125513.GF23204@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=1184089@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.