| commit | 6bfc907deed83af7c2df371ffa3508427c6de52f | |
| author | Max Reitz <mreitz@redhat.com> | |
| Wed, 29 Nov 2017 18:51:02 +0000 (29 19:51 +0100) | ||
| committer | Max Reitz <mreitz@redhat.com> | |
| Tue, 23 Jan 2018 11:34:42 +0000 (23 12:34 +0100) | ||
| tree | 3b103a79bc65f237d5f86f0e012d823a2c8d3495 | treesnapshot (tar.gz zip) |
| parent | 34ce1111416986e62fbb6d55e0a7d45bbb9802ce | commitdiff |
qemu-iotests: Fix locking issue in 102
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>
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>
| tests/qemu-iotests/102 | diffblobblamehistory | |
| tests/qemu-iotests/102.out | diffblobblamehistory |