From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: Win2003 disk corruption with kvm-1.0. and virtio
Date: Thu, 14 Feb 2013 09:27:26 +0400
Message-ID: <511C75BE.4080508@msgid.tls.msk.ru>
References: <511A520D.4@digimind.com> <201302130821.16157.hahn@univention.de> <511B6365.9050605@digimind.com> <cb0bd53a06176508603430a46b03704e@zackbummfertig.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Kvm <kvm@vger.kernel.org>,
	Sylvain Bauza <sylvain.bauza@digimind.com>
To: weber@zackbummfertig.de
Return-path: <kvm-owner@vger.kernel.org>
Received: from isrv.corpit.ru ([86.62.121.231]:60819 "EHLO isrv.corpit.ru"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751101Ab3BNF13 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 14 Feb 2013 00:27:29 -0500
In-Reply-To: <cb0bd53a06176508603430a46b03704e@zackbummfertig.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

[Please stop top-posting.  Thank you]

13.02.2013 20:03, weber@zackbummfertig.de wrote:
>
> there are known problems, WHEN  I/O "native" and cache=writethrough.

> On I/O "native" put cache to "none" otherwise your data can get broken.
> Check Redhat Pages for that.

Which problem is that?

And what is "I/O native" ?  Maybe you mean "aio", not "I/O" ?

If the talk is about aio=native, that mode does not work for regular
files, it gets "downgraded" to aio=threads automatically.  So there
should be nothing to change already.

Please elaborate.

/mjt