[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

[Miguel Enrique Cobá Martínez]

Guido Günther wrote:
> I'm using the same setup and it works fine here.
> 
> On Tue, Dec 30, 2008 at 12:22:04PM -0600, Miguel Enrique Cobá Martínez wrote:
>> unix_sock_group = "libvirt"
>> unix_sock_rw_perms = "0770"
>> auth_unix_ro = "none"
>> auth_unix_rw = "none"
> It seems you can't access the rw socket.

Yep, that was my first idea too.

> 
> You can also try:
>   cat /var/run/libvirt/libvirt-sock
> It should give "cat: /var/run/libvirt/libvirt-sock-ro: No such device or
> address" not "permission denied".
> 
Sorry, I had already test this, just not reported it. It appears ok:

miguel at laptop:~$ ls -alh /var/run/libvirt/libvirt-sock*
srwxrwx--- 1 root libvirt 0 dic 30 12:03 /var/run/libvirt/libvirt-sock
srwxrwxrwx 1 root libvirt 0 dic 30 12:03 /var/run/libvirt/libvirt-sock-ro
miguel at laptop:~$ cat /var/run/libvirt/libvirt-sock
cat: /var/run/libvirt/libvirt-sock: No existe el dispositivo o la dirección
miguel at laptop:~$ cat /var/run/libvirt/libvirt-sock-ro
cat: /var/run/libvirt/libvirt-sock-ro: No existe el dispositivo o la 
dirección

That is equivalent to the message "No such device or address".


> [..snip..] 
>> Verify that the libvirtd daemon is running with the default config:
>>
>> # ps ax| grep libvirtd
> No output here? This is wrong.

Here was my fault too. I forgot to paste the output. The daemon is 
indeed running:

miguel at laptop:~$ ps ax|grep libvirtd
  3452 ?        S      0:01 /usr/sbin/libvirtd -d
  4786 pts/0    R+     0:00 grep libvirtd


> 
> [..snip..]
>> You can only see the VMs (R/O mode: monitoring VM status only). That is, 
>> you cannot start/stop/pause the VM (R/W mode: full VM management). In 
>> the previous version you could.
>>
>> Now, as root, and using virsh you can start and stop the VM:
>>
>> laptop:~# virsh start WindowsXP
>> Domain WindowsXP started
>>
>> laptop:~# virsh shutdown WindowsXP
>> Domain WindowsXP is being shutdown
>>
>> The VM start and stop correctly and I can view it and use it with 
>> virt-manager (in R/O mode)
>>
>> But as normal user you can't start it:
>>
>> miguel at laptop:~$ virsh start WindowsXP
>> Cannot set group when not running as root
>> libvir: QEMU error : Domain not found
>> libvir: QEMU error : Domain not found
>> error: failed to get domain 'WindowsXP'
> Try "virsh -c qemu:///system".

That worked!

Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
        'quit' to quit

virsh # list
  Id Name                 State
----------------------------------

virsh # start WindowsXP
Domain WindowsXP started

After that I can see the VM started using virt-manager. Regardless, the 
problem remains, with virt-manager I can't start a VM or stop it. I must 
use virsh. The buttons from the popup menu from virt-manager for 
start/stop/pause are disabled.

I also have tried removing the connection to localhost from 
virt-manager, but after rerunning virt-manager, the same problem happens.

> 
>> Another thing I noticed, the previous version used to start the dnsmasq 
>> automatically (I had ENABLED=0 in /etc/default/dnsmasq). This versión 
>> doesn't start dnsmasq and therefore denies network capabilities to the VMs.
> This again is an indication that you're mixing access to qemu:///system
> and qemu:///session.
> 
> Please make sure you use either --connect=qemu:///system (connect to
> daemon started via /etc/init.d/libvirt-bin) or --connect=qemu:///session
> (started as user) and retest with virsh and virt-manager.
> 
> Which version of virt-manager is this? I'm using 0.6.0-6.


I'm in a clean lenny using virt-manager 0.5.4-4

> Cheers,
>  -- Guido
> 
> 

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.

Miguel Cobá