https://bugzilla.suse.com/show_bug.cgi?id=1177763 https://bugzilla.suse.com/show_bug.cgi?id=1177763#c15 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(peter.posts@gmx.n | |et) | --- Comment #15 from James Fehlig <jfehlig@suse.com> --- (In reply to Peter McDonough from comment #14)
(In reply to John Doe from comment #9)
I added myself to the libvirt group to see if it would change anything but the issue remains the same.
Solution: LIBVIRT GROUP to USER
There is no need to add your user to the libvirt group unless you set auth_unix_{ro,rw} to 'none' in /etc/libvirt/libvirtd.conf. On SUSE distros libvirtd uses polkit auth by default. Socket permissions on the read-only and read-write sockets are set to 06660, allowing anyone to connect, but they are subjected to polkit auth. The default polkit privileges allow any user to connect to read-only socket, but only root to the read-write socket. virt-manager connects to the read-write socket, so you should be prompted for root passwd if running it as a normal user. If auth on libvirtd's read-only or read-write sockets is set to 'none', then standard unix socket permissions and group membership checks apply. BTW, I'm clearing your needinfo since AFAIK we no longer need info from you :-). -- You are receiving this mail because: You are on the CC list for the bug.