[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-discuss] Failed to get "consistent read" lock on a mirroring image
From: |
Han Han |
Subject: |
[Qemu-discuss] Failed to get "consistent read" lock on a mirroring image |
Date: |
Mon, 20 Nov 2017 10:58:49 +0800 |
Hello,
On qemu-2.10, I find 'qemu-img info' couldn't get the info of a mirroring
image:
# /usr/libexec/qemu-kvm -name A -machine pc,accel=kvm \
-vnc 0.0.0.0:1 \
-monitor stdio \
-qmp tcp:0:5555,server,nowait \
-serial unix:/tmp/monitor,server,nowait \
-drive
file=/var/lib/libvirt/images/V.qcow2,format=qcow2,if=none,id=drive-virtio-blk0,werror=stop,rerror=stop
\
-device virtio-blk-pci,drive=drive-virtio-blk0,id=virtio-blk0
QEMU 2.10.0 monitor - type 'help' for more information
(qemu) drive_mirror drive-virtio-blk0 /var/lib/libvirt/images/V.new
Formatting '/var/lib/libvirt/images/V.new', fmt=qcow2 size=10737418240
cluster_size=65536 lazy_refcounts=off refcount_bits=16
# qemu-img info /var/lib/libvirt/images/V.new -U
qemu-img: Could not open '/var/lib/libvirt/images/V.new': *Failed to get
"consistent read" lock*
Is another process using the image?
But in qemu-2.9, it works. So is it expected result? Or a new feature in
qemu-2.10?
--
Han Han
Quality Engineer
Redhat.
Email: address@hidden
Phone: +861065339333
- [Qemu-discuss] Failed to get "consistent read" lock on a mirroring image,
Han Han <=