@@ -84,6 +84,7 @@ run_qemu <<EOF
"options": {
"driver": "$IMGFMT",
"id": "disk",
+ "lock-image": false,
"node-name": "test-node",
"file": {
"driver": "file",
@@ -97,6 +98,7 @@ run_qemu <<EOF
"options": {
"driver": "$IMGFMT",
"id": "disk",
+ "lock-image": false,
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -109,6 +111,7 @@ run_qemu <<EOF
"options": {
"driver": "$IMGFMT",
"id": "test-node",
+ "lock-image": false,
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -122,6 +125,7 @@ run_qemu <<EOF
"driver": "$IMGFMT",
"id": "disk2",
"node-name": "disk",
+ "lock-image": false,
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -135,6 +139,7 @@ run_qemu <<EOF
"driver": "$IMGFMT",
"id": "disk2",
"node-name": "test-node",
+ "lock-image": false,
"file": {
"driver": "file",
"filename": "$TEST_IMG"
@@ -148,6 +153,7 @@ run_qemu <<EOF
"driver": "$IMGFMT",
"id": "disk3",
"node-name": "disk3",
+ "lock-image": false,
"file": {
"driver": "file",
"filename": "$TEST_IMG"
Otherwise the error handling we are expceting will be masked by the preceding image locking check, and is going to be indistinguishable because the error messages are all the same. Signed-off-by: Fam Zheng <famz@redhat.com> --- tests/qemu-iotests/087 | 6 ++++++ 1 file changed, 6 insertions(+)