]> xenbits.xensource.com Git - libvirt.git/commitdiff
qemu.conf: Mention virtlockd in @lock_manager description
authorMichal Privoznik <mprivozn@redhat.com>
Wed, 12 Mar 2014 07:53:37 +0000 (08:53 +0100)
committerMichal Privoznik <mprivozn@redhat.com>
Thu, 13 Mar 2014 10:51:22 +0000 (11:51 +0100)
When I played with virtlockd I was stunned by lacking
documentation. My frustration got bigger when I had to
read the patches to get the correct value to set in
qemu.conf.

Moreover, from pure libvirt-pride  I'm changing commented
value from sanlock to lockd. We want to favor our own
implementation after all.

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
src/qemu/qemu.conf
src/qemu/test_libvirtd_qemu.aug.in

index e43608494c0b12622be97669a73d66c0f882fbb6..f0e802f242f681d720a3b646fc3bb942e01463f0 100644 (file)
 #allow_disk_format_probing = 1
 
 
-# To enable 'Sanlock' project based locking of the file
-# content (to prevent two VMs writing to the same
-# disk), uncomment this
+# In order to prevent accidentally starting two domains that
+# share one writable disk, libvirt offers two approaches for
+# locking files. The first one is sanlock, the other one,
+# virtlockd, is then our own implementation. Accepted values
+# are "sanlock" and "lockd".
 #
-#lock_manager = "sanlock"
+#lock_manager = "lockd"
 
 
 
index 81fedd68303cb9e1d666d6137ee7896462969d39..b2328d365ec48388acfb28aed91e58840c2a39c3 100644 (file)
@@ -64,7 +64,7 @@ module Test_libvirtd_qemu =
 { "mac_filter" = "1" }
 { "relaxed_acs_check" = "1" }
 { "allow_disk_format_probing" = "1" }
-{ "lock_manager" = "sanlock" }
+{ "lock_manager" = "lockd" }
 { "max_queued" = "0" }
 { "keepalive_interval" = "5" }
 { "keepalive_count" = "5" }