diff options
| author | Jeff Cody | 2016-02-25 18:27:29 +0100 |
|---|---|---|
| committer | Kevin Wolf | 2016-03-14 16:46:42 +0100 |
| commit | fb9245c2610932d33ce148b58714fcc7b3c6eb5f (patch) | |
| tree | 175088957c592fe81105439289aaef4e19da4c35 /docs | |
| parent | block/vpc: tests for auto-detecting VPC and Hyper-V VHD images (diff) | |
| download | qemu-fb9245c2610932d33ce148b58714fcc7b3c6eb5f.tar.gz qemu-fb9245c2610932d33ce148b58714fcc7b3c6eb5f.tar.xz qemu-fb9245c2610932d33ce148b58714fcc7b3c6eb5f.zip | |
block/vpc: give option to force the current_size field in .bdrv_create
When QEMU creates a VHD image, it goes by the original spec,
calculating the current_size based on the nearest CHS geometry (with an
exception for disks > 127GB).
Apparently, Azure will only allow images that are sized to the nearest
MB, and the current_size as calculated from CHS cannot guarantee that.
Allow QEMU to create images similar to how Hyper-V creates images, by
setting current_size to the specified virtual disk size. This
introduces an option, force_size, to be passed to the vpc format during
image creation, e.g.:
qemu-img convert -f raw -o force_size -O vpc test.img test.vhd
When using the "force_size" option, the creator app field used by
QEMU will be "qem2" instead of "qemu", to indicate the difference.
In light of this, we also add parsing of the "qem2" field during
vpc_open.
Bug reference: https://bugs.launchpad.net/qemu/+bug/1490611
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions