[Bug 585964] Re: Libvirtd -- error: monitor socket did not show up.: Connection refused

[Jamie Strandboge]

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.d/disable/usr.sbin.libvirtd'.

** Changed in: libvirt (Ubuntu)
       Status: New => Confirmed

-- 
Libvirtd  --  error: monitor socket did not show up.: Connection refused
https://bugs.launchpad.net/bugs/585964
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.