From af8d43d3933a4bec0977b9f33d69443a2d166861 Mon Sep 17 00:00:00 2001 From: Peter Lieven Date: Tue, 1 Sep 2020 14:51:29 +0200 Subject: qemu-img: avoid unaligned read requests during convert in case of large continous areas that share the same allocation status it happens that the value of s->sector_next_status is unaligned to the cluster size or even request alignment of the source. Avoid this by stripping down the s->sector_next_status position to cluster boundaries. Signed-off-by: Peter Lieven Message-Id: <20200901125129.6398-1-pl@kamp.de> [mreitz: Disable vhdx for 251] Signed-off-by: Max Reitz --- tests/qemu-iotests/251 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'tests/qemu-iotests/251') diff --git a/tests/qemu-iotests/251 b/tests/qemu-iotests/251 index 7918ba3..294773b 100755 --- a/tests/qemu-iotests/251 +++ b/tests/qemu-iotests/251 @@ -46,8 +46,11 @@ if [ "$IMGOPTSSYNTAX" = "true" ]; then # We use json:{} filenames here, so we cannot work with additional options. _unsupported_fmt $IMGFMT else - # With VDI, the output is ordered differently. Just disable it. - _unsupported_fmt vdi + # - With VDI, the output is ordered differently. Just disable it. + # - VHDX has large clusters; because qemu-img convert tries to + # align the requests to the cluster size, the output is ordered + # differently, so disable it, too. + _unsupported_fmt vdi vhdx fi -- cgit v1.1