On 2017-11-29 19:51, Max Reitz wrote: > 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 <[email protected]> > --- > tests/qemu-iotests/102 | 7 ++++++- > tests/qemu-iotests/102.out | 3 ++- > 2 files changed, 8 insertions(+), 2 deletions(-)
Applied to my block branch. Max
signature.asc
Description: OpenPGP digital signature
