Signed-off-by: river
---
.gitignore | 2 ++
src/Makefile.am | 40 +++-
src/libxl/libxl.conf| 8 +++---
src/locking/dlm.conf| 52 +
src/locking
and .pid
files. This operation could be found in libxl.
Signed-off-by: river
---
src/qemu/qemu_process.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c
index 5a364730c..49c64be6f 100644
--- a/src/qemu/qemu_process.c
+++ b/src/qemu
dlm is implemented by linux kernel, provides userspace API by
'libdlm' to lock/unlock resource, cooperated with cluster
communication software, such as corosync, could satisfy the
demands of libvirt lock manager.
Signed-off-by: river
---
configure.ac |6 +
m4/v
after unlink pid and xml files in `qemuProcessStop`
('src/qemu/qemu_process.c') to proactively tell lock manager
release locks.
Adhere to the simple, enough principle, lock information using
by running libvirt process is stored in list instead of hash
table.
I have tested i