From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>
Cc: kwolf@redhat.com, den@openvz.org, qemu-devel@nongnu.org,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] iotests: 205: support luks format
Date: Wed, 7 Feb 2018 14:40:08 -0600 [thread overview]
Message-ID: <41ec94bf-478e-a500-f6ca-e4e86923954e@redhat.com> (raw)
In-Reply-To: <3c0e7de4-5f59-f905-840f-63f7261f5af7@redhat.com>
On 02/07/2018 02:37 PM, Eric Blake wrote:
> On 02/06/2018 12:57 PM, Eric Blake wrote:
>> On 02/06/2018 12:26 PM, Daniel P. Berrangé wrote:
>>> On Tue, Feb 06, 2018 at 09:25:07PM +0300, Vladimir
>>> Sementsov-Ogievskiy wrote:
>>>> Support default luks options in VM.add_drive and in new library
>>>> function qemu_img_create. Use it in 205 iotests.
>>>>
>>>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>>> ---
>>>
>>> Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
>>
>> Thanks. I'll take this through my NBD queue.
>>
>> git git://repo.or.cz/qemu/ericb.git nbd
>>
>
> I'm seeing this failure now :(
>
> $ ./check -luks 205
> QEMU -- "/home/eblake/qemu/x86_64-softmmu/qemu-system-x86_64"
> -nodefaults -machine accel=qtest
> QEMU_IMG -- "/home/eblake/qemu/qemu-img"
> QEMU_IO -- "/home/eblake/qemu/qemu-io" --cache writeback
> QEMU_NBD -- "/home/eblake/qemu/qemu-nbd"
> IMGFMT -- luks (iter-time=10)
> IMGPROTO -- file
> PLATFORM -- Linux/x86_64 red 4.14.16-300.fc27.x86_64
> TEST_DIR -- /home/eblake/qemu/tests/qemu-iotests/scratch
> SOCKET_SCM_HELPER -- /home/eblake/qemu/tests/qemu-iotests/socket_scm_helper
>
> 205 [failed, exit status 1] - output mismatch (see 205.out.bad)
> --- /home/eblake/qemu/tests/qemu-iotests/205.out 2018-02-07
> 09:48:13.346107367 -0600
> +++ /home/eblake/qemu/tests/qemu-iotests/205.out.bad 2018-02-07
> 14:35:21.859890826 -0600
> @@ -1,5 +1,159 @@
> -.......
> +qemu-img: /home/eblake/qemu/tests/qemu-iotests/scratch/disk: Failed to
> get "write" lock
> +Is another process using the image?
Perhaps a false alarm due to a stale qemu-system-x86 process left over
from an earlier aborted test run. When I retried on a fresh system, the
test passed for me.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-02-07 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 18:25 [Qemu-devel] [PATCH v2] iotests: 205: support luks format Vladimir Sementsov-Ogievskiy
2018-02-06 18:26 ` Daniel P. Berrangé
2018-02-06 18:57 ` Eric Blake
2018-02-07 20:37 ` Eric Blake
2018-02-07 20:40 ` Eric Blake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41ec94bf-478e-a500-f6ca-e4e86923954e@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).