From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: [Qemu-devel] [PATCH] Warn if a qcow (not qcow2) file is opened Date: Tue, 30 Jun 2009 10:34:08 +0200 Message-ID: <4A49CE00.4090504@redhat.com> References: <1246284289-25394-1-git-send-email-avi@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mx2.redhat.com ([66.187.237.31]:52565 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751191AbZF3IfN (ORCPT ); Tue, 30 Jun 2009 04:35:13 -0400 In-Reply-To: <1246284289-25394-1-git-send-email-avi@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity schrieb: > The qcow block driver format is no longer maintained and likely contains > serious data corruptors. Urge users to stay away for it, and advertise > the new and improved replacement. > > Signed-off-by: Avi Kivity vvfat is using qcow internally, so the warning will appear there, too. Not that warning against vvfat would be a bad thing, but this error message could be confusing. Maybe we're lucky enough and vvfat survives a s/qcow/qcow2/, but I really never wanted to touch that code... Kevin