[Pkg-libvirt-maintainers] Bug#510235: Bug#510235: libvirt-bin: virt-manager unable to connect to libvirtd as r/w (full VM management) on a local connection

[Guido Günther]

reassign 510235 virt-manager
thanks

On Tue, Dec 30, 2008 at 01:22:54PM -0600, Miguel Enrique Cobá Martínez wrote:
> As for the symptoms, it appears that the problem is not libvirtd (at  
> least refering the startup/shutdown of VM, the dnsmasq problem remains)  
> but the way that virt-manager connects to it.
Here's the bug:

Libvirt moved the policykit file between 0.4.4 and 0.4.6 but old
virt-manager only checks one location (0.6.0 checks both):

 $ ls /usr/share/PolicyKit/policy/org.libvirt.unix.policy
 /usr/share/PolicyKit/policy/org.libvirt.unix.policy
 $ ls /usr/share/PolicyKit/policy/libvirtd.policy
 ls: cannot access /usr/share/PolicyKit/policy/libvirtd.policy: No such file or directory

virt-manager 0.5.4 checks for:

LIBVIRT_POLICY_FILE = "/usr/share/PolicyKit/policy/libvirtd.policy"

doesn't find the file and assumes a ro connection while 0.6.0 checks
for:

LIBVIRT_POLICY_FILES = [
    "/usr/share/PolicyKit/policy/libvirtd.policy",
    "/usr/share/PolicyKit/policy/org.libvirt.unix.policy"
]

The check in virt-manager is bogus anyways since you don't use policykit
but that's a different issue. I'll fix that.
Cheers,
 -- Guido