Heath Petersen | 13 Jul 05:44 2011

Unable to start libvirtd 0.9.3 on Ubuntu 10.10

I just built libvirt 0.9.3 on my Ubuntu 10.10 box.  It appears to have 
built correctly.

When I try "virsh -c qemu:///session list --all" I get the following:

error: Failed to connect socket to ' <at> /home/heath/.libvirt/libvirt-sock': 
Connection refused
error: failed to connect to the hypervisor

After that, libvirtd isn't running as user heath as it did when I was 
using 0.9.2.  When I run it with LIBVIRT_DEBUG=1 I get this:

. . .
22:26:34.334: 8385: debug : remoteOpen:774 : Auto-spawn user daemon instance
22:26:34.334: 8385: debug : doRemoteOpen:487 : proceeding with name = 
qemu:///session
22:26:34.334: 8385: debug : doRemoteOpen:497 : Connecting with transport 1
22:26:34.378: 8385: debug : doRemoteOpen:544 : Proceeding with sockname 
 <at> /home/heath/.libvirt/libvirt-sock
22:26:34.378: 8385: debug : virCommandRunAsync:1874 : About to run 
LC_ALL=C 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 
HOME=/home/heath USER=heath LOGNAME=heath /usr/local/sbin/libvirtd 
--timeout=30
22:26:34.378: 8385: debug : virCommandRunAsync:1890 : Command result 0, 
with PID 8386
22:26:34.379: 8385: debug : virCommandRun:1711 : Result status 0, 
stdout: '(null)' stderr: '(null)'
22:26:55.430: 8385: debug : do_open:1059 : driver 7 remote returned ERROR
22:26:55.430: 8385: debug : virUnrefConnect:145 : unref connection 
(Continue reading)

Matthias Bolte | 13 Jul 10:52 2011

Re: Unable to start libvirtd 0.9.3 on Ubuntu 10.10

2011/7/13 Heath Petersen <HeathPetersen <at> kandre.com>:
> I just built libvirt 0.9.3 on my Ubuntu 10.10 box.  It appears to have built
> correctly.
>
> When I try "virsh -c qemu:///session list --all" I get the following:
>
> error: Failed to connect socket to ' <at> /home/heath/.libvirt/libvirt-sock':
> Connection refused
> error: failed to connect to the hypervisor
>
> After that, libvirtd isn't running as user heath as it did when I was using
> 0.9.2.  When I run it with LIBVIRT_DEBUG=1 I get this:

Your problem is probably caused by a partly rewrite of libvirtd that
introduced a regression in the libvirtd.conf file handling. When
libvirtd is running as non-root it tries to read
$HOME/.libvirt/libvirtd.conf. Before 0.9.3 it was non-fatal if this
file wasn't there. In 0.9.3 this is fatal.

You can either touch $HOME/.libvirt/libvirtd.conf to avoid the problem
or apply this patches on top of 0.9.3 to fix it

http://libvirt.org/git/?p=libvirt.git;a=commit;h=8e2e47803c0028b42b72c45b81e91de7b0cbb7fe
http://libvirt.org/git/?p=libvirt.git;a=commit;h=a07c81c4d0befc1e92b9cf3ce25260488a6bdcdb

--

-- 
Matthias Bolte
http://photron.blogspot.com

_______________________________________________
(Continue reading)


Gmane