Hello,
virt-manager worked fine until I add myself into wheel group (for sudo), now it complain about libvirtd not running, see below for details:
$ virt-manager --debug [...SNIP...] 2011-06-06 12:54:54,429 (error:66): dialog message: Unable to open a connection to the libvirt management daemon.
Libvirt URI is: qemu:///system
Verify that: - The 'libvirtd' daemon has been started : authentication failed
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1055, in _try_open None], flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 107, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: authentication failed
2011-06-06 12:54:57,619 (engine:477): Exiting app normally.
$ virsh -c qemu:///system error: authentication failed error: failed to connect to the hypervisor
$ sudo virsh -c qemu:///system [sudo] password for athmane: Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh #
$ sudo systemctl status libvirtd.service libvirtd.service - LSB: daemon for libvirt virtualization API Loaded: loaded (/etc/rc.d/init.d/libvirtd) Active: active (running) since Mon, 06 Jun 2011 12:50:40 -0100; 12min ago Process: 3452 ExecStop=/etc/rc.d/init.d/libvirtd stop (code=exited, status=0/SUCCESS) Process: 3460 ExecStart=/etc/rc.d/init.d/libvirtd start (code=exited, status=0/SUCCESS) Main PID: 3468 (libvirtd) CGroup: name=systemd:/system/libvirtd.service ├ 1320 /usr/sbin/dnsmasq --strict-order --bind-interfaces... └ 3468 libvirtd --daemon
On 06/06/2011 10:06 AM, Athmane Madjoudj wrote:
Hello,
virt-manager worked fine until I add myself into wheel group (for sudo), now it complain about libvirtd not running, see below for details:
$ virt-manager --debug [...SNIP...] 2011-06-06 12:54:54,429 (error:66): dialog message: Unable to open a connection to the libvirt management daemon.
Libvirt URI is: qemu:///system
Verify that:
- The 'libvirtd' daemon has been started
: authentication failed
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1055, in _try_open None], flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 107, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: authentication failed
2011-06-06 12:54:57,619 (engine:477): Exiting app normally.
$ virsh -c qemu:///system error: authentication failed error: failed to connect to the hypervisor
$ sudo virsh -c qemu:///system [sudo] password for athmane: Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh #
$ sudo systemctl status libvirtd.service libvirtd.service - LSB: daemon for libvirt virtualization API Loaded: loaded (/etc/rc.d/init.d/libvirtd) Active: active (running) since Mon, 06 Jun 2011 12:50:40 -0100; 12min ago Process: 3452 ExecStop=/etc/rc.d/init.d/libvirtd stop (code=exited, status=0/SUCCESS) Process: 3460 ExecStart=/etc/rc.d/init.d/libvirtd start (code=exited, status=0/SUCCESS) Main PID: 3468 (libvirtd) CGroup: name=systemd:/system/libvirtd.service ├ 1320 /usr/sbin/dnsmasq --strict-order --bind-interfaces... └ 3468 libvirtd --daemon
I'm guessing that's a policykit problem, please file a bug against policykit. But for all I know it could be expected behavior :)
Thanks, Cole