On 03/21/2011 03:02 PM, Kevin Wolf wrote:
Am 21.03.2011 13:23, schrieb Avi Kivity:
> On 03/09/2011 07:38 PM, Anthony Liguori wrote:
>> On 03/09/2011 11:27 AM, Christoph Hellwig wrote:
>>> On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
Quoting the bug report:
Am 21.03.2011 13:23, schrieb Avi Kivity:
> On 03/09/2011 07:38 PM, Anthony Liguori wrote:
>> On 03/09/2011 11:27 AM, Christoph Hellwig wrote:
>>> On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
Quoting the bug report:
qemu ensures that guest writes and qemu metadata
On 03/09/2011 07:38 PM, Anthony Liguori wrote:
On 03/09/2011 11:27 AM, Christoph Hellwig wrote:
On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
Quoting the bug report:
qemu ensures that guest writes and qemu metadata writes hit the
disk
when necessary to prevent data cor
On 03/09/2011 11:27 AM, Christoph Hellwig wrote:
On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
Quoting the bug report:
qemu ensures that guest writes and qemu metadata writes hit the disk
when necessary to prevent data corruption. However, if an image was
in host pa
On Wed, Mar 09, 2011 at 05:15:53PM +0100, Kevin Wolf wrote:
> Quoting the bug report:
>
> qemu ensures that guest writes and qemu metadata writes hit the disk
> when necessary to prevent data corruption. However, if an image was
> in host pagecache prior to starting qemu, for example a
Quoting the bug report:
qemu ensures that guest writes and qemu metadata writes hit the disk
when necessary to prevent data corruption. However, if an image was
in host pagecache prior to starting qemu, for example after running
qemu-img convert, then nothing prevents writes from r
