From: IdaRub <idarub@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] loadvm on a read only image
Date: Mon, 19 Feb 2007 10:46:57 -0800 [thread overview]
Message-ID: <a6df7cca0702191046j2fef001dv8e33479f6bf5fe17@mail.gmail.com> (raw)
I would like to be able to restore a snapshot from a disk image file
with read only permissions, for example stored on a cdrom.
QEMU checks if an image supports snapshots (bdrv_can_snapshot, etc)
and will fail if the disk is read only. As a quick test, I patched
out these checks and QEMU will boot the snapshot, but it will hang
after a little while eating 100% cpu. My guess would be this is some
timer to flush data back to disk, but I haven't looked into it at all.
The -snapshot option does support snapshots on read only images,
however when looking for snapshot it looks in the newly created
temporary backing file. This is nice because you can create/delete
snapshots in a sandbox, but you can't restore a snapshot stored in the
original disk image.
Any ideas on what would be easier/better, trying to restore snapshots
in the base image with -snapshot, or trying to make QEMU support
snapshots on a read only image?
Thanks
reply other threads:[~2007-02-19 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a6df7cca0702191046j2fef001dv8e33479f6bf5fe17@mail.gmail.com \
--to=idarub@gmail.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).