From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=54283 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OHCk3-0007Fd-DG for qemu-devel@nongnu.org; Wed, 26 May 2010 05:17:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OHCk2-0003yX-3J for qemu-devel@nongnu.org; Wed, 26 May 2010 05:17:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62119) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OHCk1-0003yK-Mr for qemu-devel@nongnu.org; Wed, 26 May 2010 05:17:34 -0400 Message-ID: <4BFCE707.1010503@redhat.com> Date: Wed, 26 May 2010 11:16:55 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] Add cache=volatile parameter to -drive References: <1274091292-4812-1-git-send-email-agraf@suse.de> <4BF14CE9.5040907@suse.de> <4BF15DC8.8080104@codemonkey.ws> <201005171723.15675.paul@codesourcery.com> <4BF16E22.6090400@codemonkey.ws> <4BFC0FF6.1080005@suse.de> <20100525210113.GE1402@hall.aurel32.net> <4BFC79E8.1070700@codemonkey.ws> <20100526085248.GC21913@volta.aurel32.net> In-Reply-To: <20100526085248.GC21913@volta.aurel32.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aurelien Jarno Cc: qemu-devel@nongnu.org, Paul Brook , Alexander Graf , hch@lst.de Am 26.05.2010 10:52, schrieb Aurelien Jarno: > On Tue, May 25, 2010 at 08:31:20PM -0500, Anthony Liguori wrote: >> On 05/25/2010 04:01 PM, Aurelien Jarno wrote: >>> >>> I really think this patch can be useful, in my own case when testing >>> debian-installer (I already cache=writeback). In short all that is about >>> developing and testing, as opposed to run a VM in production, can >>> benefit about that. This was one of the original use case of QEMU before >>> KVM arrived. >>> >>> Unless someone can convince me not to do it, I seriously considering >>> applying this patch. >> >> There really needs to be an indication in the --help output of what >> the ramifications of this option are, in the very least. It should > > That's indeed something than can be done, but to avoid double standards, > it should also be done for other features that can lead to data > corruption. I am talking for example on the qcow format, which is not > really supported anymore. That said, qcow1 is probably in a better state than half of the other drivers. Basically only raw and qcow2 are really maintained, you'd need to warn about any other format then. Kevin