Hi all,
can't find any evidence in the VMDK spec that there is a possibility of
having a smaller grain anywhere, including at the end of the image.
There is one value in the header which defines the grain size, which
typically is 64K.
The spec is rather clear that the total capacity of an imag
On 2/18/2016 6:25 PM, Christian Svensson wrote:
>
> On Thu, Feb 18, 2016 at 4:35 PM, Michal Necasek
> mailto:michal.neca...@oracle.com>> wrote:
>
>According to my reading of it, qemu-img produced an rater suspect
> image. You have a supposedly 64K grain but after decompression, there is
On Thu, Feb 18, 2016 at 4:35 PM, Michal Necasek
wrote:
> According to my reading of it, qemu-img produced an rater suspect
> image. You have a supposedly 64K grain but after decompression, there is
> only 49K of data. That's obviously a problem because what do you do with
> the missing 15K? You
Hi Christian,
You can read the specification yourself at
https://www.vmware.com/support/developer/vddk/vmdk_50_technote.pdf
According to my reading of it, qemu-img produced an rater suspect
image. You have a supposedly 64K grain but after decompression, there is
only 49K of data. Th
Hi,
I was debugging why my VMware products were able to accept an OVA but not
VirtualBox.
Turns out that the problem was that my underlying hard drive image was not
aligned to the grain size (128 sectors in my case) and that caused
VirtualBox to throw VERR_VD_VMDK_INVALID_FORMAT.
For the record, t
