From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Alex Bligh <alex@alex.org.uk>, Kaveh Razavi <kaveh@cs.vu.nl>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Introduce cache images for the QCOW2 format
Date: Thu, 15 Aug 2013 15:50:45 +0800 [thread overview]
Message-ID: <520C8855.3020707@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130814153216.GN4583@dhcp-200-207.str.redhat.com>
于 2013-8-14 23:32, Kevin Wolf 写道:
> Am 14.08.2013 um 16:26 hat Kaveh Razavi geschrieben:
>> On 08/14/2013 03:50 PM, Alex Bligh wrote:
>>> Assuming the cache quota is not exhausted, how do you know how that
>>> a VM has finished 'creating' the cache? At any point it might
>>> read a bit more from the backing image.
>>
>> I was assuming on shutdown.
>
> Wait, so you're not really changing the cache while it's used, but you
> only create it once and then use it like a regular backing file? If so,
> the only thing we need to talk about is the creation, because there's no
> difference for using it.
>
> Creation can use the existing copy-on-read functionality, and the only
> thing you need additionally is a way to turn copy-on-read off at the
> right point.
>
> Or do I misunderstand what you're doing?
>
> Kevin
>
This cache capability seems have little to do with qcow2, but a
general block function: start/stop copy on read for one BS in a backing
chain. If so, suggest:
1 refine existing general copy on read code, not in qcow2.c but general
block code, make it able to start/stop copy on read for a BDS in the
chain.
2 add qmp interface for it.
Then the work flow will be:
step 1: prepare image, not related to qcow2 format.
qemu-img create cache.img -b base.img
qemu-img create vm1.img -b cache.img
step 2: boot vm1, vm2:
qemu -hda vm1.img -COR cache.img
qemu -hda vm2.img
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2013-08-15 7:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 17:03 [Qemu-devel] [PATCH] Introduce cache images for the QCOW2 format Kaveh Razavi
2013-08-13 21:37 ` Eric Blake
2013-08-14 11:13 ` Kaveh Razavi
2013-08-13 22:53 ` Alex Bligh
2013-08-14 11:28 ` Kaveh Razavi
2013-08-14 11:52 ` Fam Zheng
2013-08-14 12:03 ` Alex Bligh
2013-08-14 15:58 ` Richard W.M. Jones
2013-08-15 0:53 ` Fam Zheng
2013-08-15 5:51 ` Alex Bligh
2013-08-14 11:57 ` Alex Bligh
2013-08-14 13:37 ` Kaveh Razavi
2013-08-13 23:16 ` Alex Bligh
2013-08-14 11:42 ` Kaveh Razavi
2013-08-14 12:02 ` Alex Bligh
2013-08-14 13:43 ` Kaveh Razavi
2013-08-14 13:50 ` Alex Bligh
2013-08-14 14:26 ` Kaveh Razavi
2013-08-14 15:02 ` Alex Bligh
2013-08-14 15:32 ` Kevin Wolf
2013-08-15 7:50 ` Wenchao Xia [this message]
2013-08-15 8:11 ` Stefan Hajnoczi
2013-08-14 9:29 ` Stefan Hajnoczi
2013-08-14 14:20 ` Kaveh Razavi
2013-08-15 8:32 ` Stefan Hajnoczi
2013-08-15 12:25 ` Kaveh Razavi
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=520C8855.3020707@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=alex@alex.org.uk \
--cc=kaveh@cs.vu.nl \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.