e74ee02c1e
The output of qemu-io changed recently - most tests have been fixed in commit36b9986b08("tests/qemu-iotests: Fix output of qemu-io related tests") already, but a qcow1, vmdk, and nbd test were still missing. Fixes:99e98d7c9f("qemu-io: Use error_[gs]et_progname()") Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <20190501134127.21104-1-thuth@redhat.com> [eblake: squash in NBD 083 fixes] Reviewed-by: Stefano Garzarella <sgarzare@redhat.com> Tested-by: Stefano Garzarella <sgarzare@redhat.com> Signed-off-by: Eric Blake <eblake@redhat.com>
27 lines
1.3 KiB
Plaintext
27 lines
1.3 KiB
Plaintext
QA output created by 092
|
|
|
|
== Invalid cluster size ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Cluster size must be between 512 and 64k
|
|
|
|
== Invalid L2 table size ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
|
|
qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
|
|
qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
|
|
qemu-io: can't open device TEST_DIR/t.qcow: L2 table size must be between 512 and 64k
|
|
|
|
== Invalid size ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Image too large
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Image too large
|
|
|
|
== Invalid backing file length ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Backing file name too long
|
|
qemu-io: can't open device TEST_DIR/t.qcow: Backing file name too long
|
|
*** done
|