also hit this issue with a clean setup, but not sure how to reproduce, since I've setup multiple server with the same "script", but only one server hit the problem, and problem still after applying the workaround mention in #34
here's how I setup the services, 1. apt-get install qemu-kvm 2. apt-get install libvirt-bin 3. boot up VMs, and make sure it is running ( virsh list --all ) 4. reboot host 5. wait for server start-up 6. login, check service libvirt-bin running state => not running, and VMs not start, of course 7. try to apply the workaround mention in #34, trick of apparmor_parser -r / -R 8. reboot again 9. login, check service libvirt-bin running state => running (at the first time) 10. reboot again 11. login, check service libvirt-bin running state => not running (seems like workaround not always works?) look into the `syslog`, each time libvirt-bin unsuccessful start-up at boot, it will have the following log in syslog, ==> Apr 16 21:02:09 host2 kernel: [ 313.059830] init: libvirt-bin post- start process (2430) terminated with status 1 and here's my system information, $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty $ uname -a Linux host2 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux hope these information could help, reference: - https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/comments/34 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386465 Title: apparmor profile prevents libvirtd from creating a socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
