Quoting Jamie Strandboge (<email address hidden>):
> This is an interesting error:
> error: Failed to connect socket to '@/home/tucxnXJm/.libvirt/libvirt-sock': Connection refused
> error: failed to connect to the hypervisor
>
> This is a new location of the socket. Do you have any apparmor denials
> in kern.log?
No, the only thing I saw was several entries like:
Sep 2 13:39:24 sergelap kernel: [19175.248710] type=1400 audit(1314988764.860:26): apparmor="STATUS" operation="profile_remove" info="profile does not exist" error=-2 name="/usr/sbin/libvirtd" pid=6460 comm="apparmor_parser"
Quoting Jamie Strandboge (<email address hidden>): tucxnXJm/ .libvirt/ libvirt- sock': Connection refused
> This is an interesting error:
> error: Failed to connect socket to '@/home/
> error: failed to connect to the hypervisor
>
> This is a new location of the socket. Do you have any apparmor denials
> in kern.log?
No, the only thing I saw was several entries like:
Sep 2 13:39:24 sergelap kernel: [19175.248710] type=1400 audit(131498876 4.860:26) : apparmor="STATUS" operation= "profile_ remove" info="profile does not exist" error=-2 name="/ usr/sbin/ libvirtd" pid=6460 comm="apparmor_ parser"