Re: [Qemu-devel] [PATCH v4 0/2] vmdk: Implement bdrv_get_specific_info

[Max Reitz <mreitz@redhat.com>]

On 18.10.2013 05:12, Fam Zheng wrote:
> The new information looks like:
>
>     image: /tmp/foo.vmdk
>     file format: vmdk
>     virtual size: 100G (107374182400 bytes)
>     disk size: 4.0K
>     Format specific information:
>         cid: 0
>         create_type: twoGbMaxExtentFlat
>         parent cid: 0
>         extents:
>             [0]:
>                 virtual size: 2147483648
>                 filename: /tmp/foo-f001.vmdk
>                 format: FLAT
>             [1]:
>                 virtual size: 2147483648
>                 filename: /tmp/foo-f002.vmdk
>                 format: FLAT
>             [2]:
>                 virtual size: 2147483648
>                 filename: /tmp/foo-f003.vmdk
>                 format: FLAT
>             [3]:                                           ...
> v4: Rebase to master.
>     Free create_type if open fails. (Stefan)
>     Set create_type for monolithcSparse in no description file case.
>
> v3: Rebase to kevin's block branch.
>
>
> Fam Zheng (2):
>   qapi: Add optional field 'compressed' to ImageInfo
>   vmdk: Implment bdrv_get_specific_info
>
>  block/vmdk.c               | 64 +++++++++++++++++++++++++++++++++++++++++++++-
>  qapi-schema.json           | 28 ++++++++++++++++++--
>  tests/qemu-iotests/059     |  2 +-
>  tests/qemu-iotests/059.out |  5 ++--
>  4 files changed, 92 insertions(+), 7 deletions(-)

Ping – is there something that prevents this from being merged? Eric
reviewed it and I'd personally like to have it upstream. ;-)

Max