From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41179) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VMwqu-0006i3-TO for qemu-devel@nongnu.org; Fri, 20 Sep 2013 05:18:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VMwqq-00065V-3P for qemu-devel@nongnu.org; Fri, 20 Sep 2013 05:18:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:16413) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VMwqp-00065I-SM for qemu-devel@nongnu.org; Fri, 20 Sep 2013 05:18:12 -0400 Date: Fri, 20 Sep 2013 11:18:14 +0200 From: Kevin Wolf Message-ID: <20130920091814.GC2800@dhcp-200-207.str.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 2/2] block: qemu-iotests for vhdx, read sample dynamic imagee List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex =?iso-8859-1?Q?Benn=E9e?= Cc: Jeff Cody , famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com Am 20.09.2013 um 11:10 hat Alex Benn=E9e geschrieben: >=20 > jcody@redhat.com writes: >=20 > > This adds the VHDX format to the qemu-iotests format, and adds > > a read test. The test reads from an existing sample image, that > > was created with Hyper-V under Windwos Server 2012. > > > > The image file is a 1GB dynamic image, with 32MB blocks. > > > > The pattern 0xa5 exists from 0MB-33MB (past a block size boundary) > > > > The pattern 0x96 exists from 33MB-66MB (past another block boundary, > > and leaving a partial blank block) > > > > From 66MB-1024MB, all reads should return 0. > > > > Although 1GB dynamic image with 66MB of data, the bzip2'ed image > > file size is only 874 bytes. >=20 > I take it there is additional meta-data in there generated by Windows > Server itself? Otherwise I would be tempted to write a tool to generate > the image on demand so it could be used to trigger other edge cases whe= n > found. >=20 > Having said that 874 bytes certainly isn't to heavy a burden for the > repository ;-) Eventually, qemu-img will be able to create VHDX images, but I think the point is that we compare against real Hyper-V VHDX images to ensure that we're really reading the spec the same way as they do. > I'm currently pondering what the best way of supporting system images > (i.e. kernel+rootfs) would be to make system regression testing easier. > Unfortunately those images would be far too large to carry in the repo > although there may be some sub-module annex type thing I could try. Sounds like you're looking for qemu-tests? http://git.qemu.org/?p=3Dqemu-test.git;a=3Dsummary Kevin