Re: [libvirt] [PATCH v4 00/23] Introduce metadata locking
Michal Privoznik <mprivozn(a)redhat.com> [2018-09-27, 10:14AM +0200]:
Right, so this is just waiting for virtlockd to lock the paths.
virtlockd is obviously unable to do that (as I suggested in my previous
e-mail - is perhaps some other process holding the lock?).
It can not lock the paths, because those paths are already locked by the
first domain. This is intentional. But it should take 60 seconds to
resolve this and block the whole libvirt daemon in the process.
Can you please enable debug logs for virtlockd, reproduce and share
the
log with me? Setting this in /etc/libvirt/virtlockd.conf should be enough:
log_level=1
log_filters="4:event 3:rpc"
log_outputs="1:file:/var/log/virtlockd.lod"
See attached.
Attachments:
- signature.asc (application/pgp-signature — 902 bytes)
- virtlockd.log.gz (application/gzip — 42.9 KB)