forked from pool/libvirt
a870a15461
- Introduce virtlockd daemon
- parallels: add disk and network device support
- Add virDomainSendProcessSignal API
- Introduce virDomainFSTrim() public API
- add fuse support for libvirt lxc
- Add Gluster protocol as supported network disk backend
- various snapshot improvements
- Add upstream patches to fix bugs in 1.0.1
66ff2ddc-virtlockd-systemd-file-perms.patch,
462a6962-script-fixes1.patch, cb854b8f-script-fixes2.patch,
5ec4b22b-script-fixes3.patch, a1fd56cb-script-fixes4.patch,
68e7bc45-libxl-link-fix.patch
- Rework SUSE patches for the various init scripts
Dropped use-init-script-redhat.patch and added
libvirtd-init-script.patch, libvirt-guests-init-script.patch,
and virtlockd-init-script.patch
- Drop upstream patches: 371ddc98-xen-sysctl-9.patch,
416eca18-xenstore-header-fix.patch,
f644361b-virCommand-env.patch, 2b32735a-virCommand-env.patch,
9785f2b6-fix-xen-sysctl9.patch
OBS-URL: https://build.opensuse.org/package/show/Virtualization/libvirt?expand=0&rev=238
38 lines
1.4 KiB
Diff
38 lines
1.4 KiB
Diff
Index: libvirt-1.0.1/src/qemu/qemu.conf
|
|
===================================================================
|
|
--- libvirt-1.0.1.orig/src/qemu/qemu.conf
|
|
+++ libvirt-1.0.1/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
|
|
@@ -357,6 +366,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
|