[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH for-2.12] qemu-iotests: Fix locking issue in 102
From: |
Max Reitz |
Subject: |
Re: [Qemu-devel] [PATCH for-2.12] qemu-iotests: Fix locking issue in 102 |
Date: |
Wed, 17 Jan 2018 14:29:45 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 |
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 <address@hidden>
> ---
> 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Qemu-devel] [PATCH for-2.12] qemu-iotests: Fix locking issue in 102,
Max Reitz <=