Hi,
On Mon, 31 Aug 2020 14:51:35 -0600 Joel Johnson <mrj...@lixil.net> wrote:
Version: 5.0.0-4+deb10u1
I ran into this same issue on a buster system, with additional
buster-backports packages installed. After digging through it appears
that during a recent update the libvirt-daemon-system package was
uninstalled without me noticing. Reinstalling the package also resolved
the issue for me.
Because of an other problem with a vagrant box and debian buster
i tried to reproduce that issue on a newly installed debian bullseye.
Now i run into this issue.
sudo debsums --config | grep -v OK
/etc/sudoers FAILED
id
uid=1004(beschat) gid=1004(beschat)
Gruppen=1004(beschat),1005(libvirtd),64055(libvirt-qemu)
$ echo $VAGRANT_DEFAULT_PROVIDER
libvirt
Bringing machine 'default' up with 'libvirt' provider...
Error while connecting to Libvirt: Error making a connection to libvirt
URI qemu:///system?no_verify=1&keyfile=/home/beschat/.ssh/id_rsa:
Call to virConnectOpen failed: authentication unavailable: no polkit
agent available to authenticate action 'org.libvirt.unix.manage'
dpkg -l | grep polkit
ii gir1.2-polkit-1.0 0.105-29
amd64 GObject introspection data for PolicyKit
ii libpolkit-agent-1-0:amd64 0.105-29
amd64 PolicyKit Authentication Agent API
ii libpolkit-gobject-1-0:amd64 0.105-29
amd64 PolicyKit Authorization API
ii libpolkit-qt5-1-1:amd64 0.113.0-1
amd64 PolicyKit-qt5-1 library
sudo cat /var/lib/polkit-1/localauthority/10-vendor.d/60-libvirt.pkla
[Allow group libvirt management permissions]
Identity=unix-group:libvirt
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes
--
Bernd
