File suse-qemu-conf.patch of Package libvirt

Overview Repositories Revisions Requests Users Attributes Meta

File suse-qemu-conf.patch of Package libvirt (Revision 5704a2b70952e2487e286c0c8e837afb)

Currently displaying revision 5704a2b70952e2487e286c0c8e837afb , Show latest

Index: libvirt-0.10.2/src/qemu/qemu.conf
===================================================================
--- libvirt-0.10.2.orig/src/qemu/qemu.conf
+++ libvirt-0.10.2/src/qemu/qemu.conf
@@ -169,7 +169,16 @@
 # a special value; security_driver can be set to that value in
 # isolation, but it cannot appear in a list of drivers.
 #
+# SUSE Note:
+# Currently, Apparmor is the default security framework in SUSE
+# distros.  If Apparmor is enabled on the host, libvirtd is
+# generously confined but users must opt-in to confine qemu
+# instances.  Change this to 'apparmor' to enable Apparmor
+# confinement of qemu instances.
+#
 #security_driver = "selinux"
+#security_driver = "apparmor"
+security_driver = "none"
 
 # If set to non-zero, then the default security labeling
 # will make guests confined. If set to zero, then guests
@@ -342,6 +351,15 @@
 #allow_disk_format_probing = 1
 
 
+# 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

Places

File suse-qemu-conf.patch of Package libvirt (Revision 5704a2b70952e2487e286c0c8e837afb)

Places