summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMax Reitz2021-01-20 11:20:43 +0100
committerMax Reitz2021-01-26 14:36:37 +0100
commit67a066fbe4070449fb63a5d44ae2e78a05a1e53d (patch)
treefdd5f4d29c1ed39a2a6eae675a4df91077e1a481
parentiotests: 56: prepare for backup over block-copy (diff)
downloadqemu-67a066fbe4070449fb63a5d44ae2e78a05a1e53d.tar.gz
qemu-67a066fbe4070449fb63a5d44ae2e78a05a1e53d.tar.xz
qemu-67a066fbe4070449fb63a5d44ae2e78a05a1e53d.zip
iotests/129: Limit backup's max-chunk/max-workers
Right now, this does not change anything, because backup ignores max-chunk and max-workers. However, as soon as backup is switched over to block-copy for the background copying process, we will need it to keep 129 passing. Signed-off-by: Max Reitz <mreitz@redhat.com> Message-Id: <20210120102043.28346-1-mreitz@redhat.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
-rwxr-xr-xtests/qemu-iotests/1297
1 files changed, 6 insertions, 1 deletions
diff --git a/tests/qemu-iotests/129 b/tests/qemu-iotests/129
index 2f7b28d4a0..5251e2669e 100755
--- a/tests/qemu-iotests/129
+++ b/tests/qemu-iotests/129
@@ -71,9 +71,14 @@ class TestStopWithBlockJob(iotests.QMPTestCase):
sync="full", buf_size=65536)
def test_drive_backup(self):
+ # Limit max-chunk and max-workers so that block-copy will not
+ # launch so many workers working on so much data each that
+ # stop's bdrv_drain_all() would finish the job
self.do_test_stop("drive-backup", device="drive0",
target=self.target_img, format=iotests.imgfmt,
- sync="full")
+ sync="full",
+ x_perf={ 'max-chunk': 65536,
+ 'max-workers': 8 })
def test_block_commit(self):
# Add overlay above the source node so that we actually use a