From: Michael Coppola <michael.n.coppola@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1184089] Re: [Feature request] loadvm snapshot as read-only
Date: Mon, 27 May 2013 22:42:17 -0000 [thread overview]
Message-ID: <20130527224217.26583.40786.malone@wampee.canonical.com> (raw)
In-Reply-To: 20130525082911.27253.67454.malonedeb@gac.canonical.com
Awesome, looking forward to it. I may be misunderstanding what's
happening under the hood, but at least for me, calling 'loadvm' on a
single snapshot over and over seems to work the first few times and then
immediately blue screens the WinXP guest with PFN_LIST_CORRUPT. I was
under the assumption that all runtime modifications were being written
back to the image, effectively "corrupting" something (whether it was
changes to the snapshot or the "backing image" causing things to break).
Until then, I've seemed to have found a workaround for the feature
itself. Instead of creating a snapshot with 'savevm', I can start the
VM with -snapshot and then call:
migrate "exec: gzip -c > snapshot.gz"
in QMP and it saves the live image to a compressed file. Make sure it's
completed migration before exiting with "info migrate". Subsequently
loading the snapshot with:
qemu-* <whatever flags> -incoming "exec: gzip -c -d snapshot.gz"
-snapshot
will load the live snapshot and redirect all runtime modifications to a
temp file. http://www.linux-kvm.org/page/Migration says not to use
-snapshot, but who follows the rules anyways? ;) It seems to work so
far and things haven't exploded yet. Running md5sum on the qcow2 image
and gzip snapshot before and after shows no changes to either files.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1184089
Title:
[Feature request] loadvm snapshot as read-only
Status in QEMU:
New
Bug description:
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.
I found a lot of discussion about this topic on the mailing list years
ago, including some patch submissions, but none of the conversations
panned out.
http://lists.gnu.org/archive/html/qemu-discuss/2011-10/msg00011.html
http://copilotco.com/mail-archives/qemu.2008/msg00072.html
http://web.archiveorange.com/archive/v/1XS1vcusGInZKG2e0ImX
http://marc.info/?l=qemu-devel&m=117191084713590
What would it take for this feature to be added, and can we use the
patches submitted by Eddie Kohler to enable this feature?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1184089/+subscriptions
next prev parent reply other threads:[~2013-05-27 22:50 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
2013-05-27 22:42 ` Michael Coppola [this message]
2013-05-28 8:22 ` [Qemu-devel] [Bug 1184089] " 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=20130527224217.26583.40786.malone@wampee.canonical.com \
--to=michael.n.coppola@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 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).