From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33575) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aamEN-0005CL-54 for qemu-devel@nongnu.org; Tue, 01 Mar 2016 10:28:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aamEM-0005sv-69 for qemu-devel@nongnu.org; Tue, 01 Mar 2016 10:28:59 -0500 Date: Tue, 1 Mar 2016 16:28:50 +0100 From: Kevin Wolf Message-ID: <20160301152850.GG4250@noname.str.redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v3 0/4] VHD/VPC format compatibility List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jeff Cody Cc: pl@kamp.de, qemu-devel@nongnu.org, qemu-block@nongnu.org Am 25.02.2016 um 18:27 hat Jeff Cody geschrieben: > Changes from v3: > > Patch 2: Added a sample image & tests for Disk2vhd > Patch 3: When using force_size, set the CHS geometry to max > (as Disk2vhd does), to maximize backward compatibility (thanks Peter) > Patch 4: Updated test results due to the above changes in patch 3 > > Changes from v2: > > Patches 2,4: Just use qemu-io instead of a qemu instance (thanks Kevin, Max) > Patch 3: Use "qem2" for the creator app field, when forcing the size (thanks Kevin) > > This is a long-standing issue that has come up many times, and has had > several different patches posted to fix it. Virtual PC, and Hyper-V > calculate the disk geometry differently for VHD, leading to compatibility > issues. > > We want to fix these compatibility problems, however we want to make sure > we do not break backwards compatibility. > > There are two areas of compatibility addressed: > > * Reading images (Patch 1) > * Creating images (Patch 3) > > Please see the commit messages in Patches 1,3 for details. Thanks, applied to the block branch. Kevin