On Thu, Mar 11, 2010 at 12:19 PM, Tom Georgoulias <tomg@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > As test user "testu": > > [testu@kvm ~]$ virsh -c qemu:///system list --all > error: unable to connect to '/var/run/libvirt/libvirt-sock': Permission > denied > error: failed to connect to the hypervisor > [testu@kvm ~]$ virsh -c qemu:///session list --all > 15:04:05.167: error : No vport operation path found for host0 > 15:04:05.186: error : No vport operation path found for host4 > 15:04:05.192: error : No vport operation path found for host3 > 15:04:05.240: error : No vport operation path found for host1 > 15:04:05.240: error : No vport operation path found for host2 > Id Name State > ---------------------------------- > > [testu@kvm ~]$ > > Doesn't seem like a socket access issue, the perms for the > libvirt-sock-ro are wide open. It says "unable to connect to '/var/run/libvirt/libvirt-sock'", not to 'libvirt-sock-ro'. Try manually changing it to look like: srwxrwx--- 1 root testu 0 Mar 11 15:03 libvirt-sock [This is how mine is configured] Akemi _______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-virt
