qemu/tests/qemu-iotests/182.out

QA output created by 182
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=33554432
Starting QEMU

Starting a second QEMU using the same image should fail
QEMU_PROG: -drive file=TEST_DIR/t.qcow2,if=none,id=drive0,file.locking=on: Failed to get "write" lock
Is another process using the image [TEST_DIR/t.qcow2]?
*** done
tests: Add POSIX image locking test case 182 Signed-off-by: Fam Zheng <famz@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com> 2017-05-02 19:35:58 +03:00			`QA output created by 182`
			`Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=33554432`
			`Starting QEMU`

			`Starting a second QEMU using the same image should fail`
			`QEMU_PROG: -drive file=TEST_DIR/t.qcow2,if=none,id=drive0,file.locking=on: Failed to get "write" lock`
file-posix: Include filename in locking error message Image locking errors happening at device initialization time doesn't say which file cannot be locked, for instance, -device scsi-disk,drive=drive-1: Failed to get shared "write" lock Is another process using the image? could refer to either the overlay image or its backing image. Hoist the error_append_hint to the caller of raw_check_lock_bytes where file name is known, and include it in the error hint. Signed-off-by: Fam Zheng <famz@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com> 2018-09-25 08:05:01 +03:00			`Is another process using the image [TEST_DIR/t.qcow2]?`
tests: Add POSIX image locking test case 182 Signed-off-by: Fam Zheng <famz@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com> 2017-05-02 19:35:58 +03:00			`*** done`