2014-05-08 20:12:42 +02:00
|
|
|
QA output created by 089
|
|
|
|
|
|
|
|
|
|
=== Testing nested image formats ===
|
|
|
|
|
|
2014-12-09 08:38:03 +01:00
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=67108864
|
2014-05-08 20:12:42 +02:00
|
|
|
wrote 512/512 bytes at offset 0
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 512/512 bytes at offset 512
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 512/512 bytes at offset 1024
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 0
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 512
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 1024
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Pattern verification failed at offset 0, 512 bytes
|
|
|
|
|
read 512/512 bytes at offset 0
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
|
2018-02-24 16:40:32 +01:00
|
|
|
=== Testing correct handling of 'backing':null ===
|
|
|
|
|
|
iotests: Specify explicit backing format where sensible
There are many existing qcow2 images that specify a backing file but
no format. This has been the source of CVEs in the past, but has
become more prominent of a problem now that libvirt has switched to
-blockdev. With older -drive, at least the probing was always done by
qemu (so the only risk of a changed format between successive boots of
a guest was if qemu was upgraded and probed differently). But with
newer -blockdev, libvirt must specify a format; if libvirt guesses raw
where the image was formatted, this results in data corruption visible
to the guest; conversely, if libvirt guesses qcow2 where qemu was
using raw, this can result in potential security holes, so modern
libvirt instead refuses to use images without explicit backing format.
The change in libvirt to reject images without explicit backing format
has pointed out that a number of tools have been far too reliant on
probing in the past. It's time to set a better example in our own
iotests of properly setting this parameter.
iotest calls to create, rebase, and convert are all impacted to some
degree. It's a bit annoying that we are inconsistent on command line
- while all of those accept -o backing_file=...,backing_fmt=..., the
shortcuts are different: create and rebase have -b and -F, while
convert has -B but no -F. (amend has no shortcuts, but the previous
patch just deprecated the use of amend to change backing chains).
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20200706203954.341758-9-eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
2020-07-06 22:39:52 +02:00
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
2018-02-24 16:40:32 +01:00
|
|
|
read 512/512 bytes at offset 0
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 0
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
|
2014-05-08 20:12:42 +02:00
|
|
|
=== Testing blkdebug ===
|
|
|
|
|
|
2014-12-09 08:38:03 +01:00
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
2014-05-08 20:12:42 +02:00
|
|
|
wrote 512/512 bytes at offset 229376
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read failed: Input/output error
|
|
|
|
|
|
|
|
|
|
=== Testing qemu-img info output ===
|
|
|
|
|
|
|
|
|
|
image: TEST_DIR/t.IMGFMT
|
|
|
|
|
file format: IMGFMT
|
2019-04-17 19:11:01 +02:00
|
|
|
virtual size: 64 MiB (67108864 bytes)
|
2014-05-08 20:12:42 +02:00
|
|
|
cluster_size: 65536
|
|
|
|
|
|
|
|
|
|
=== Testing option merging ===
|
|
|
|
|
|
|
|
|
|
format name: IMGFMT
|
|
|
|
|
cluster size: 64 KiB
|
|
|
|
|
vm state offset: 512 MiB
|
|
|
|
|
format name: IMGFMT
|
|
|
|
|
cluster size: 64 KiB
|
|
|
|
|
vm state offset: 512 MiB
|
|
|
|
|
*** done
|