[Pkg-libvirt-maintainers] Bug#557744: Bug#557744: libvirt-bin: Starting domain fails with "qemudOpenMonitorUnix: monitor socket did not show up.: Connection refused"

[Guido Günther]

On Sun, Nov 22, 2009 at 02:24:36PM +0100, Vadim Zeitlin wrote:
> Package: libvirt-bin
> Version: 0.7.2-3
> Severity: important
> 
> 
> Running "virsh -c qemu:///system create vm.xml" fails with
> 
> 	error: Failed to create domain from vm.xml
> 	error: monitor socket did not show up.: Connection refused
> 
> and
> 
> 	kernel: [ 2863.481686] device vnet0 entered promiscuous mode
> 	kernel: [ 2863.483550] virbr0: topology change detected, propagating
> 	kernel: [ 2863.483555] virbr0: port 1(vnet0) entering forwarding state
> 	kernel: [ 2863.599974] virbr0: port 1(vnet0) entering disabled state
> 	kernel: [ 2863.630507] device vnet0 left promiscuous mode
> 	kernel: [ 2863.630513] virbr0: port 1(vnet0) entering disabled state
> 	libvirtd: 14:08:22.683: error : qemudOpenMonitorUnix:1007 : monitor socket did not show up.: Connection refused
> 
> in syslog. The symptoms are identical when running this command as a normal
> user (member of libvirt group) or root.
> 
> Unfortunately I was unable to find out which socket it wants to connect to,
> all I can say is that it is _not_ /var/run/libvirt/libvirt-sock as it does
> connect to it successfully.
> 
> Looking at qemudOpenMonitorUnix() in libvirt Git it seems like the error is
> indeed given from there but, mysteriously, I don't see these socket() and
> connect() calls neither with strace nor gdb so I just don't understand
> what's going on here at all. Any pointers in the right direction would be
> appreciated.
You can run the daemon with 

VIRT_DEBUG=1 libvirtd

to find out what happens. Strace might help to. It's doing fine here.
Please also have a look at the VM logs in /var/log/libvirt/.
 -- Guido