6f3c90af3c
Mixing byte offset and sector allocation counts is a bit confusing. Also, reporting n/m sectors, where m decreases according to the remaining size of the file, isn't really adding any useful information; and reporting an offset at both the front and end of the line, with large amounts of whitespace, is pointless. Update the output to use byte counts and shorter lines, then adjust the affected tests (./check -qcow2 102, ./check -vpc 146). Note that 'qemu-io map' is MUCH weaker than 'qemu-img map'; the former only shows which regions of the active layer are allocated, without regards to where the allocation comes from or whether the allocated portion is known to read as zero (because it is using the weaker bdrv_is_allocated()); while the latter (especially in --output=json mode) reports more details from bdrv_get_block_status(). Signed-off-by: Eric Blake <eblake@redhat.com> Message-id: 20170429191419.30051-4-eblake@redhat.com Reviewed-by: Max Reitz <mreitz@redhat.com> Signed-off-by: Max Reitz <mreitz@redhat.com>
71 lines
1.9 KiB
Plaintext
71 lines
1.9 KiB
Plaintext
QA output created by 146
|
|
|
|
=== Testing VPC Autodetect ===
|
|
|
|
126.998 GiB (0x1fbfe04000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing VPC with current_size force ===
|
|
|
|
127 GiB (0x1fc0000000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing VPC with chs force ===
|
|
|
|
126.998 GiB (0x1fbfe04000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing Hyper-V Autodetect ===
|
|
|
|
127 GiB (0x1fc0000000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing Hyper-V with current_size force ===
|
|
|
|
127 GiB (0x1fc0000000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing Hyper-V with chs force ===
|
|
|
|
126.998 GiB (0x1fbfe04000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing d2v Autodetect ===
|
|
|
|
251.250 MiB (0xfb40000) bytes allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing d2v with current_size force ===
|
|
|
|
251.250 MiB (0xfb40000) bytes allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing d2v with chs force ===
|
|
|
|
251.250 MiB (0xfb40000) bytes allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing Image create, default ===
|
|
|
|
Formatting 'TEST_DIR/IMGFMT-create-test.IMGFMT', fmt=IMGFMT size=4294967296
|
|
|
|
=== Read created image, default opts ====
|
|
|
|
4 GiB (0x10007a000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Read created image, force_size_calc=chs ====
|
|
|
|
4 GiB (0x10007a000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Read created image, force_size_calc=current_size ====
|
|
|
|
4 GiB (0x10007a000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Testing Image create, force_size ===
|
|
|
|
Formatting 'TEST_DIR/IMGFMT-create-test.IMGFMT', fmt=IMGFMT size=4294967296 force_size=on
|
|
|
|
=== Read created image, default opts ====
|
|
|
|
4 GiB (0x100000000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Read created image, force_size_calc=chs ====
|
|
|
|
4 GiB (0x100000000) bytes not allocated at offset 0 bytes (0x0)
|
|
|
|
=== Read created image, force_size_calc=current_size ====
|
|
|
|
4 GiB (0x100000000) bytes not allocated at offset 0 bytes (0x0)
|
|
*** done
|