2017-03-31 20:53:54 +02:00
|
|
|
QA output created by 176
|
|
|
|
|
|
2017-11-17 17:47:47 +01:00
|
|
|
=== Test pass snapshot.0 ===
|
2017-03-31 20:53:54 +02:00
|
|
|
|
2017-03-31 20:53:56 +02:00
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-03-31 20:53:54 +02:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Image committed.
|
|
|
|
|
read 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
2017-11-17 17:47:47 +01:00
|
|
|
Snapshot list:
|
|
|
|
|
ID TAG
|
|
|
|
|
1 snap
|
2017-03-31 20:53:54 +02:00
|
|
|
|
2017-11-17 17:47:47 +01:00
|
|
|
=== Test pass snapshot.1 ===
|
2017-03-31 20:53:54 +02:00
|
|
|
|
2017-03-31 20:53:56 +02:00
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-03-31 20:53:54 +02:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Image committed.
|
|
|
|
|
read 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x10000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x7fff0000 0x10000 TEST_DIR/t.IMGFMT
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT
|
2017-11-17 17:47:47 +01:00
|
|
|
Snapshot list:
|
|
|
|
|
ID TAG
|
|
|
|
|
1 snap
|
2017-03-31 20:53:54 +02:00
|
|
|
|
2017-11-17 17:47:47 +01:00
|
|
|
=== Test pass snapshot.2 ===
|
2017-03-31 20:53:54 +02:00
|
|
|
|
2017-03-31 20:53:56 +02:00
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-03-31 20:53:54 +02:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Image committed.
|
|
|
|
|
read 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x10000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x7fff0000 0x10000 TEST_DIR/t.IMGFMT
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT
|
2017-11-17 17:47:47 +01:00
|
|
|
Snapshot list:
|
|
|
|
|
ID TAG
|
|
|
|
|
1 snap
|
2017-03-31 20:53:54 +02:00
|
|
|
|
2017-11-17 17:47:47 +01:00
|
|
|
=== Test pass snapshot.3 ===
|
2017-03-31 20:53:54 +02:00
|
|
|
|
2017-03-31 20:53:56 +02:00
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-03-31 20:53:54 +02:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Image committed.
|
|
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:56 +02:00
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.base
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.base
|
2017-03-31 20:53:54 +02:00
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x10000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x7fff0000 0x10000 TEST_DIR/t.IMGFMT
|
2017-03-31 20:53:56 +02:00
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT
|
2017-11-17 17:47:47 +01:00
|
|
|
Snapshot list:
|
|
|
|
|
ID TAG
|
|
|
|
|
1 snap
|
|
|
|
|
|
|
|
|
|
=== Test pass bitmap.0 ===
|
|
|
|
|
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-11-17 17:47:47 +01:00
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-11-17 17:47:47 +01:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Image committed.
|
|
|
|
|
read 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2017-11-17 20:04:22 +01:00
|
|
|
{"return": {"sha256": HASH}}
|
2017-11-17 17:47:47 +01:00
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-11-17 17:47:47 +01:00
|
|
|
|
|
|
|
|
=== Test pass bitmap.1 ===
|
|
|
|
|
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-11-17 17:47:47 +01:00
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-11-17 17:47:47 +01:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Image committed.
|
|
|
|
|
read 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x10000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x7fff0000 0x10000 TEST_DIR/t.IMGFMT
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT
|
|
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2017-11-17 20:04:22 +01:00
|
|
|
{"return": {"sha256": HASH}}
|
2017-11-17 17:47:47 +01:00
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-11-17 17:47:47 +01:00
|
|
|
|
|
|
|
|
=== Test pass bitmap.2 ===
|
|
|
|
|
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-11-17 17:47:47 +01:00
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-11-17 17:47:47 +01:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Image committed.
|
|
|
|
|
read 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x10000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x7fff0000 0x10000 TEST_DIR/t.IMGFMT
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT
|
|
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2017-11-17 20:04:22 +01:00
|
|
|
{"return": {"sha256": HASH}}
|
2017-11-17 17:47:47 +01:00
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-11-17 17:47:47 +01:00
|
|
|
|
|
|
|
|
=== Test pass bitmap.3 ===
|
|
|
|
|
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=2202010112
|
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.itmd', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2202010112 backing_file=TEST_DIR/t.IMGFMT.itmd backing_fmt=IMGFMT
|
2017-11-17 17:47:47 +01:00
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-11-17 17:47:47 +01:00
|
|
|
wrote 196608/196608 bytes at offset 2147287040
|
|
|
|
|
192 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 131072/131072 bytes at offset 2147352576
|
|
|
|
|
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Image committed.
|
|
|
|
|
read 65536/65536 bytes at offset 2147287040
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147352576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 65536/65536 bytes at offset 2147418112
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 512/512 bytes at offset 2202009600
|
|
|
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x30000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x20000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
Offset Length File
|
|
|
|
|
0x7ffd0000 0x10000 TEST_DIR/t.IMGFMT.base
|
|
|
|
|
0x7ffe0000 0x10000 TEST_DIR/t.IMGFMT.itmd
|
|
|
|
|
0x7fff0000 0x10000 TEST_DIR/t.IMGFMT
|
|
|
|
|
0x83400000 0x200 TEST_DIR/t.IMGFMT
|
|
|
|
|
QMP_VERSION
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{"return": {}}
|
2017-11-17 20:04:22 +01:00
|
|
|
{"return": {"sha256": HASH}}
|
2017-11-17 17:47:47 +01:00
|
|
|
{"return": {}}
|
2018-12-05 12:01:31 +01:00
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
2017-03-31 20:53:54 +02:00
|
|
|
*** done
|