From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [Qemu-devel] [RFC] Disk integrity in QEMU Date: Sun, 12 Oct 2008 16:35:46 +0100 Message-ID: <20081012153546.GD18814@shareable.org> References: <48EE38B9.2050106@codemonkey.ws> <48EF1D55.7060307@redhat.com> <48F0E83E.2000907@redhat.com> <48F10DFD.40505@codemonkey.ws> <20081012004401.GA9763@acer.localdomain> <48F1CF9E.9030500@redhat.com> <48F20BBC.1040708@il.qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Chris Wright , Mark McLoughlin , Ryan Harper , kvm-devel , Laurent Vivier To: qemu-devel@nongnu.org Return-path: Received: from mail2.shareable.org ([80.68.89.115]:57243 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752938AbYJLPhQ (ORCPT ); Sun, 12 Oct 2008 11:37:16 -0400 Content-Disposition: inline In-Reply-To: <48F20BBC.1040708@il.qumranet.com> Sender: kvm-owner@vger.kernel.org List-ID: Dor Laor wrote: > Actually this is what happens on mainline qemu with cache=off. Have I understood right that cache=off on a qcow2 image only uses O_DIRECT for the leaf image, and the chain of base images don't use O_DIRECT? Sometimes on a memory constrained host, where the (collective) guest memory is nearly as big as the host memory, I'm not sure this is what I want. -- Jamie