You are not logged in.
after upgrading to libvirt 0.10.2-4
i am getting this error:
Policy kit denied action org.libvirt.unix.manage
my /etc/polkit-1/localauthority/50-local.d/org.libvirt.unix.manage.pkla
havent change at all
[Allow fred libvirt management permissions]
Identity=unix-group:kvm
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes
$ id ebal
uid=374(ebal) gid=374(ebal) groups=374(ebal),92(audio),78(kvm)
any ideas ?
Last edited by ebal (2012-11-01 06:19:50)
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
Access to the kvm device node is already taken care of by the udev uaccess tag. So you need not be in the kvm group. Whether or not this will have an effect on your access, I have no idea.
Offline
@WonderWoofy How is your response relevant to my question ?
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
Did you read the error you were given? You are saying basically that you have a permissions issue. So I am telling you that under systemd, the permissions granted by being in the kvm group (which you apparently saw as significant to post) are now taken care of by udev and the uaccess tag. So you no longer need to be in the kvm group. Sometimes (I am not saying that this is necessarily one of those times), being in the group while uaccess as also taking care of it, can cause issues. Hence the recommendation in the systemd wiki page that you remove yourself from most groups. To see what udev takes care of with the uaccess tag, look at /usr/lib/udev/rules/70-uaccess.rules.
Offline
@WonderWoofy I am thankful that your are trying to answering me, but you are off topic.
I am getting the same error msg from libvirtd either using
Identity=unix-group:kvm
or
Identity=unix-user:ebal
this isnt relevant with systemd or udev.
as root:
# libvirtd -v
as user:
$ virsh -c qemu:///system
and libvirtd inform me with the above msg error.
Last edited by ebal (2012-10-31 15:09:19)
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline
I got the same error. The reason is because of the version change of polkit to version 0.107. You have to refer to the section in the libvirt archwiki page for polkit >= 0.107.
I'd paste a link, but I can't seem to figure out how to do that in Luakit.
Thanks,
railmaniac
Offline
It works for me. I think that now that it is trying to bind to a socket, you have to start libvirtd with the proper service file, (# systemctl start libvirtd). Railmaniac's suggestion that you look at the wiki is also probably relevent, as polkit has changed the format of its config files.
Offline
The "polkit >= 0.107" was the problem.
Thanks for the hint.
https://balaskas.gr
Linux System Engineer - Registered Linux User #420129
Offline