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 <vsement...@virtuozzo.com>
---
Reviewed-by: Daniel P. Berrange <berra...@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
