This does not only affect qemu-img only, it could not make libvirt
"" work either when two vms were running with share disk
image. Is there a workaround for this situation?
Best,
Liang
On 10/6/17 10:30 AM, Daniel Berrange wrote:
> I've just noticed, however, that '--force-share' appears
I've just noticed, however, that '--force-share' appears totally
undocumented in both CLI help output and the man page. So that's
certainly something that should be fixed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
The QEMU process that has the disk image open may be doing I/O that
causes qcow2 metadata to be changed. Such changes could confuse the
'qemu-img' process it is was reading the metadata at the same time it
was being changed, causing bad data to be printed or worse. So requiring
a write lock is the
