From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49906) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xwtz5-0001Kn-1M for qemu-devel@nongnu.org; Fri, 05 Dec 2014 09:35:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xwtyy-0002Sh-R9 for qemu-devel@nongnu.org; Fri, 05 Dec 2014 09:35:50 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42388) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xwtyy-0002SZ-GV for qemu-devel@nongnu.org; Fri, 05 Dec 2014 09:35:44 -0500 Date: Fri, 5 Dec 2014 09:35:38 -0500 From: Jeff Cody Message-ID: <20141205143538.GB2433@localhost.localdomain> References: <1417775209-11812-1-git-send-email-kwolf@redhat.com> <20141205110719.GB6040@noname.str.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141205110719.GB6040@noname.str.redhat.com> Subject: Re: [Qemu-devel] [PATCH] vhdx: Return true for bdrv_has_zero_init List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: amulya.lokesha@emc.com, qemu-devel@nongnu.org, stefanha@redhat.com, mreitz@redhat.com On Fri, Dec 05, 2014 at 12:07:19PM +0100, Kevin Wolf wrote: > Am 05.12.2014 um 11:26 hat Kevin Wolf geschrieben: > > Like for most other image formats, vhdx images read as all zero in qemu > > after their creation (we're taking advantage from the fact that qemu has > > just created the image, because PAYLOAD_BLOCK_NOT_PRESENT actually means > > undefined rather than zeroed according to the spec). > > Brain fart, self-NACK. > > This obviously means that 'qemu-img convert' still can't leave zeros in > the source file unwritten in the destination, otherwise we're corrupting > data. qemu would still read them correctly, but other implementations > might not. > > We'd have to write the BAT for dynamic images with PAYLOAD_BLOCK_ZERO > for all clusters before we can make this change. > > Jeff, do you want to fix this? > Yes, I'll go ahead and put together a patch(es) for that.