From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: KVM call agenda for October 25 Date: Wed, 26 Oct 2011 10:15:52 +0200 Message-ID: <4EA7C1B8.9000903@redhat.com> References: <4EA6ACFE.6090109@redhat.com> <4EA6B41B.3000903@codemonkey.ws> <4EA6C00B.3030701@redhat.com> <4EA6C25C.8000502@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Paolo Bonzini , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Anthony Liguori Return-path: In-Reply-To: <4EA6C25C.8000502@codemonkey.ws> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org Am 25.10.2011 16:06, schrieb Anthony Liguori: > On 10/25/2011 08:56 AM, Kevin Wolf wrote: >> Am 25.10.2011 15:05, schrieb Anthony Liguori: >>> I'd be much more open to changing the default mode to cache=none FWIW since the >>> risk of data loss there is much, much lower. >> >> I think people said that they'd rather not have cache=none as default >> because O_DIRECT doesn't work everywhere. > > Where doesn't it work these days? I know it doesn't work on tmpfs. I know it > works on ext[234], btrfs, nfs. Besides file systems (and probably OSes) that don't support O_DIRECT, there's another case: Our defaults don't work on 4k sector disks today. You need to explicitly specify the logical_block_size qdev property for cache=none to work on them. And changing this default isn't trivial as the right value doesn't only depend on the host disk, but it's also guest visible. The only way out would be bounce buffers, but I'm not sure that doing that silently is a good idea... Kevin