pool/libvirt
SHA256
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- Improve lock manager comments in qemu.conf

Browse Source 
Updated suse-qemu-conf.patch

OBS-URL: https://build.opensuse.org/package/show/Virtualization/libvirt?expand=0&rev=357
This commit is contained in:
James Fehlig 2014-03-04 19:05:01 +00:00 committed by Git OBS Bridge
parent 4d81ed52ea
commit e3d360d0d4
2 changed files with 30 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libvirt.changes
View File

@ -1,3 +1,9 @@
-------------------------------------------------------------------
Tue Mar 4 11:43:25 MST 2014 - jfehlig@suse.com
- Improve lock manager comments in qemu.conf
Updated suse-qemu-conf.patch
-------------------------------------------------------------------
Tue Mar 4 17:03:47 UTC 2014 - speilicke@suse.com

35
suse-qemu-conf.patch
View File

@ -19,19 +19,32 @@ Index: libvirt-1.2.2/src/qemu/qemu.conf
# If set to non-zero, then the default security labeling
# will make guests confined. If set to zero, then guests
@@ -402,6 +411,15 @@
@@ -402,10 +411,25 @@
#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
+# SUSE note:
+# Many lock managers, sanlock included, will kill the resources
+# they protect when terminated. E.g. the sanlock daemon will kill
+# any virtual machines for which it holds disk leases when the
+# daemon is stopped or restarted. Administrators must be vigilant
+# when enabling a lock manager since simply updating the manager
+# may cause it to be restarted, potentially killing the resources
+# it protects.
+# Two lock managers are supported: lockd and sanlock. lockd, which
+# is provided by the virtlockd service, uses advisory locks (flock(2))
+# to protect virtual machine disks. sanlock uses the notion of leases
+# to protect virtual machine disks and is more appropriate in a SAN
+# environment.
+#
# To enable 'Sanlock' project based locking of the file
# content (to prevent two VMs writing to the same
# disk), uncomment this
+# For most deployments that require virtual machine disk protection,
+# lockd is recommended since it is easy to configure and the virtlockd
+# service can be restarted without terminating any running virtual
+# machines. sanlock, which may be preferred in some SAN environments,
+# has the disadvantage of not being able to be restarted without
+# first terminating all virtual machines for which it holds leases.
+#
+# To enable lockd or sanlock based protection of virtual machine disk
+# content (to prevent two VMs writing to the same disk), uncomment one
+# of the following
#
+#lock_manager = "lockd"
#lock_manager = "sanlock"