6bfc907dee
102 truncates a qcow2 file (the raw file) on purpose while a VM is running. However, image locking will usually prevent exactly this. The fact that most people have not noticed until now (I suppose you may have seen sporadic failures, but not taken them too seriously, like me) further shows that this truncation is actually not really done concurrently, but that the VM is still starting up by this point and has not yet opened the image. Remedy this by waiting for the monitor shell to appear before the qemu-img invocation so we know the VM is up. Signed-off-by: Max Reitz <mreitz@redhat.com> Message-id: 20171129185102.29390-1-mreitz@redhat.com Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Max Reitz <mreitz@redhat.com>
23 lines
730 B
Plaintext
23 lines
730 B
Plaintext
QA output created by 102
|
|
|
|
=== Testing map command on truncated image ===
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=65536
|
|
wrote 65536/65536 bytes at offset 0
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
Image resized.
|
|
64 KiB (0x10000) bytes allocated at offset 0 bytes (0x0)
|
|
Offset Length Mapped to File
|
|
|
|
=== Testing map on an image file truncated outside of qemu ===
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=65536
|
|
wrote 65536/65536 bytes at offset 0
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
QEMU X.Y.Z monitor - type 'help' for more information
|
|
Image resized.
|
|
(qemu)
|
|
(qemu) qemu-io drv0 map
|
|
64 KiB (0x10000) bytes allocated at offset 0 bytes (0x0)
|
|
*** done
|