[Pkg-libvirt-maintainers] Bug#597158: Bug#597158: somewhat working

Guido Günther agx at sigxcpu.org
Thu Sep 30 15:08:30 UTC 2010


On Thu, Sep 30, 2010 at 08:20:54PM +0530, Praveen A wrote:
> > Sep 17 11:56:01 savannah kernel: [ 2255.650679] attempt to access beyond end of device
> 
> > Your system looks broken here. What is /dev/sdb1?
> 
> This is unrelated message, there is no message related to libvirtd in
> /var/log/messages.
> 
> 
> What does
> 
> 
>  /usr/sbin/libvirtd --verbose
> 
Thats a start.

> pravi at savannah:~$ sudo /usr/sbin/libvirtd --verbose
> 19:48:21.377: warning : qemudStartup:1832 : Unable to create cgroup
> for driver: No such device or address
> 19:48:21.496: warning : lxcStartup:1895 : Unable to create cgroup for
> driver: No such device or address
> 
> When I click on 'localhost (QEMU)' connection, I get the following message
> 
> 19:49:46.730: error : storagePoolLookupByName:299 : Storage pool not
> found: no pool with matching name 'default'
> 19:49:46.735: error : storagePoolLookupByName:299 : Storage pool not
> found: no pool with matching name 'default'
> 19:49:46.785: error : virLibConnError:448 : this function is not
> supported by the connection driver: virConnectNumOfInterfaces
Thats all pretty normal.

> When I restart, I get qemu working, but only when I start libvirtd
> manually (/etc/init.d/libvirt-bin is not able to start libvirtd)
Please try to find out why this is happening, don't use virt-manager vor
that but virsh as described on the debugging page.

How does libvirt fail if you use the /etc/init.d/libvirt-bin? Try strace
or add the --verbose option to /etc/default/libvirt-bin.
Cheers,
 -- Guido`





More information about the Pkg-libvirt-maintainers mailing list