From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Feature request for qcow v2
Date: Sun, 23 Jul 2006 15:51:06 -0500 [thread overview]
Message-ID: <44C3E13A.1070509@codemonkey.ws> (raw)
Hi,
I've been playing with some code to implement an HTTP block device in
QEMU. I'll post when I've got something working. As I am building this
though, I thought of something that would be nice to have for qcow v2.
What I'd like is essentially a copy-on-read flag. If this flag is set,
and there is a base image, then whenever a read occurs to an unallocated
sector, the sector is copied from the base (similar to a write) and the
sector is allocated.
The idea is that copy-on-read is useful when read is really slow (for
instance, with an HTTP block device). This way, you could essentially
always use qcow + HTTP so that your block device was locally cached. It
seems a bit more elegant than trying to implement a caching mechanism in
the HTTP block device.
Regards,
Anthony Liguori
reply other threads:[~2006-07-23 20:51 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=44C3E13A.1070509@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).