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

- Add a note in /etc/libvirt/qemu.conf describing administrator

Browse Source 
vigilance required when enabling a lock manager such as sanlock

OBS-URL: https://build.opensuse.org/package/show/Virtualization/libvirt?expand=0&rev=200
This commit is contained in:
James Fehlig 2012-02-16 17:05:01 +00:00 committed by Git OBS Bridge
parent afbbb95406
commit 61bad01df3
3 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libvirt.changes
View File

@ -1,3 +1,9 @@
-------------------------------------------------------------------
Thu Feb 16 09:59:52 MST 2012 - jfehlig@suse.com
- Add a note in /etc/libvirt/qemu.conf describing administrator
vigilance required when enabling a lock manager such as sanlock
-------------------------------------------------------------------
Thu Feb 16 09:01:58 MST 2012 - jfehlig@suse.com

1
libvirt.spec
View File

@ -15,7 +15,6 @@
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
# For now, default to a full server + client build
%define client_only 0

16
suse-qemu-conf.patch
View File

@ -19,3 +19,19 @@ Index: libvirt-0.9.10/src/qemu/qemu.conf
# If set to non-zero, then the default security labeling
# will make guests confined. If set to zero, then guests
@@ -316,6 +325,15 @@
# max_processes = 0
# max_files = 0
+# 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.
+#
# To enable 'Sanlock' project based locking of the file
# content (to prevent two VMs writing to the same
# disk), uncomment this