Comment 12 for bug 585964
Revision history for this message
| Jamie Strandboge (jdstrand) wrote Re: Libvirtd -- error: monitor socket did not show up.: Connection refused | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Revised test case:
1. install libvirt-bin and test that a VM can start
2. apt-get purge apparmor
3. reboot
4. try to start a VM
WORKAROUND: simply disabling apparmor via 'security=""' with or without purging seems to work fine. I also noticed that subsequent reboots seemed to work ok (which is a little weird).
Unless you have a specific reason to do so, I *highly* recommend using AppArmor with libvirt. If you really need to disable AppArmor with libvirt, I suggest only disabling the profile instead of all of AppArmor. AppArmor protects several applications in the default install. If you only want to disable AppArmor for libvirt, adjust qemu.conf to use 'security = none' or do: 'sudo touch /etc/apparmor.