diff options
| author | Fam Zheng <famz@redhat.com> | 2013-06-26 17:24:32 +0800 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2013-06-28 09:20:27 +0200 |
| commit | 8ed610a1c983dd2ed1eed8841036af55751d115f (patch) | |
| tree | 78b655653f4f7b36799527f253d32035e4aa09ff /block/cow.c | |
| parent | 8ab6feec2c7500faafd9a4571fb40d03dd360a64 (diff) | |
| download | qemu-8ed610a1c983dd2ed1eed8841036af55751d115f.zip qemu-8ed610a1c983dd2ed1eed8841036af55751d115f.tar.gz qemu-8ed610a1c983dd2ed1eed8841036af55751d115f.tar.bz2 | |
vmdk: remove wrong calculation of relative path
When creating image with backing file, the driver tries to calculate the
relative path from created image file to backing file, but the path
computation is incorrect. e.g.:
$ qemu-img create -f vmdk -b vmdk-data-disk.vmdk vmdk-data-snapshot1
Formatting 'vmdk-data-snapshot1', fmt=vmdk size=10737418240
backing_file='vmdk-data-disk.vmdk' compat6=off zeroed_grain=off
$ qemu-img info vmdk-data-snapshot1
image: vmdk-data-snapshot1
file format: vmdk
virtual size: 10G (10737418240 bytes)
disk size: 12K
-> backing file: disk.vmdk
The common part in file names, "vmdk-data-", is incorrectly forgotten by
relative_path(). As the VMDK specification has no restriction on
parentNameHint to be relative path, we simply remove this by using the
backing_file option.
Cc: qemu-stable@nongnu.org
Signed-off-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block/cow.c')
0 files changed, 0 insertions, 0 deletions