From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35477) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VB4lr-0005nX-85 for qemu-devel@nongnu.org; Sun, 18 Aug 2013 11:20:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VB4lm-0005yf-BI for qemu-devel@nongnu.org; Sun, 18 Aug 2013 11:19:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:3458) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VB4lm-0005yO-3f for qemu-devel@nongnu.org; Sun, 18 Aug 2013 11:19:54 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r7IFJrYB003776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 18 Aug 2013 11:19:53 -0400 Message-ID: <5210E5EE.9020107@redhat.com> Date: Sun, 18 Aug 2013 17:19:10 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1376356869-19417-1-git-send-email-famz@redhat.com> <1376356869-19417-2-git-send-email-famz@redhat.com> In-Reply-To: <1376356869-19417-2-git-send-email-famz@redhat.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 1/4] vmdk: fix L1 and L2 table size in vmdk3 open List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com Il 13/08/2013 03:21, Fam Zheng ha scritto: > VMDK3 header has the field l1dir_size, but vmdk_open_vmdk3 hardcoded the > value. This patch honors the header field. > > And the L2 table size is 4096 according to VMDK spec[1], instead of > 1 << 9 (512). I'm not sure from the VMDK spec that _only_ 4096 is supported for VMDK3 files. The way I read it, VMDK3 files in hosted products are supposed to have 2K grain tables (as specified by vmdk_open_vmdk3). Perhaps we can check if L1size * 64 is enough to cover the whole file, and if not use 4096? Paolo > [1]: > http://www.vmware.com/support/developer/vddk/vmdk_50_technote.pdf?src=vmdk