From: Anthony Liguori <anthony@codemonkey.ws>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Storage requirements for live migration
Date: Fri, 11 Nov 2011 17:23:42 -0600 [thread overview]
Message-ID: <4EBDAE7E.4080907@codemonkey.ws> (raw)
In-Reply-To: <20111111224318.GC6036@us.ibm.com>
On 11/11/2011 04:43 PM, Ryan Harper wrote:
>> == Image Formats ==
>>
>> Image formats are not safe to use with live migration. The reason is that
>> QEMU caches data for image formats and does not have a mechanism to flush
>> those caches. The following attempts to describe the issues with the
>> various formats
>>
>> === QCOW2 ===
>>
>> QCOW2 caches two forms of data, cluster metadata (L1/L2 data, refcount
>> table, etc) and mutable header information (file size, snapshot entries,
>> etc).
>>
>> This data needs to be discarded before after migration starts.
>
> before after?
>
> pick one =)
Er, the sentence is intelligible with either word. I've updated the wiki with
something that actually makes sense :-)
Regards,
Anthony Liguori
>
>
prev parent reply other threads:[~2011-11-11 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 0:11 [Qemu-devel] Storage requirements for live migration Anthony Liguori
2011-11-11 6:27 ` Mark Wu
2011-11-11 9:15 ` Kevin Wolf
2011-11-11 9:38 ` Kevin Wolf
2011-11-11 9:55 ` Daniel P. Berrange
2011-11-11 10:01 ` Kevin Wolf
2011-11-11 14:08 ` Anthony Liguori
2011-11-11 14:05 ` Anthony Liguori
2011-11-11 22:43 ` Ryan Harper
2011-11-11 23:23 ` Anthony Liguori [this message]
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=4EBDAE7E.4080907@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=ryanh@us.ibm.com \
--cc=stefanha@linux.vnet.ibm.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.