Bug ID | 1125841 |
---|---|
Summary | AppArmor security driver not enabled for QEMU in libvirt |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | openSUSE Factory |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Virtualization:Tools |
Assignee | virt-bugs@suse.de |
Reporter | supercoolemail@seznam.cz |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Safari/537.36 Build Identifier: Setting security_driver = "apparmor" in /etc/libvirt/qemu.conf or enabling apparmor individually per domain leads to error with libvirt 5: Security driver apparmor not enabled Reproducible: Always Steps to Reproduce: 1. Set apparmor as security driver in /etc/libvirt/qemu.conf . 2. Use libvirt to start QEMU domain. Actual Results: Error: Security driver apparmor not enabled Failed to initialize security drivers Initialization of QEMU state driver failed: internal error: Failed to initialize security drivers Expected Results: Domain would start and be confined by AppArmor as it used to be before libvirt 5.