Hi,
I think there are two different issues. One is the PolicyKit setup as
you nicely explained, but the error which is indicating that you might
have the problem is:
"virsh # connect qemu:///system
error: Failed to connect to the hypervisor
error: authentication failed: authentication failed"
Thanks for the info!
Do you mind if we add this to the documentation?
On Tue, Feb 21, 2012 at 10:51 AM, jan horacek wrote:
> Hello,
>
>> [oneadmin at nubacesga-01-2 libvirt]$ virsh list
>> error: Failed to reconnect to the hypervisor
>> error: no valid connection
>> error: Failed to connect sock
Hello,
> [oneadmin at nubacesga-01-2 libvirt]$ virsh list
> error: Failed to reconnect to the hypervisor
> error: no valid connection
> error: Failed to connect socket to
> '@/srv/cloud/one/.libvirt/libvirt-sock': Connection refused
there are more ways to solve it, the one is to disable PolicyKit
Hi
I have a recent implementation on CentOS 6.2, and everything works perfect,
i had the same problem, you need configurate libvirt permission on each
hypervisor.
Check the followintg files:
/etc/libvirt/qemu.conf
/etc/libvirt/libvirtd.conf
/etc/sysconfig/libvirtd
On Wed, Feb 1, 2012 at 8:59 AM
Seems to be a problem related to a new security stuff named "PolicyKit".
It is used by default in CentOS 6
Here the references:
http://wiki.libvirt.org/page/SSHPolicyKitSetup
http://practicallyvirtual.wordpress.com/2011/12/17/authentication-failed-when-running-virsh-as-non-root/
Regards
Hi:
We just reinstall a node with CentOS 6.2
After add the host to OpenNebula, the host state is "error"
The problem seems to be a permission issue:
This is the result when we run "virsh list" command with the user
oneadmin in this node:
[oneadmin@nubacesga-01-2 libvirt]$ virsh list
err
