On Fri, Aug 08, 2008 at 11:49:46AM +0200, Stefan de Konink wrote: > It is a trivial error, but i wonder if: > > Failed to change group ownership of /var/run/libvirt > Failed to bind socket to '/var/run/libvirt/libvirt-sock': No such file or > directory > > > This could be corrected to: > > /var/run/libvirt doesn't exist > or an mkdir is done on the directory... I see install -d -m 0755 $RPM_BUILD_ROOT%{_localstatedir}/run/libvirt/ in libvirt spec file and mkdir -p $(DESTDIR)$(localstatedir)/run/libvirt in qemud/Makefile.am as part of install-data-local rule. So it seems it really should be created appropriately as part of 'make install'

a better reporting of the error would be fine, but something else went wrong first.

On Fri, Aug 08, 2008 at 12:08:05PM +0200, Stefan de Konink wrote: > On Fri, 8 Aug 2008, Daniel Veillard wrote: > > > > install -d -m 0755 $RPM_BUILD_ROOT%{_localstatedir}/run/libvirt/ > > > > in libvirt spec file and > > > > mkdir -p $(DESTDIR)$(localstatedir)/run/libvirt > > > > in qemud/Makefile.am as part of install-data-local rule. So it seems > > it really should be created appropriately as part of 'make install' > > My /var/run is empty upon boot. (ramfs) One may wonder why libvirt needs a > dedicated directory at all for two sockets... That just happens to be your particular deployment scenario. Other hypervisor drivers put stuff in there too, hence we have a directory.

Dan/Dan, any reason we can't 'mkdir' this when libvirtd starts up?

On Fri, Aug 08, 2008 at 12:08:05PM +0200, Stefan de Konink wrote: > My /var/run is empty upon boot. (ramfs) One may wonder why libvirt needs a > dedicated directory at all for two sockets... This seems to be a valid point. Note that /var/run/libvirt is also used for temporary files, and I think some of the hypervisor drivers can put stuff there too, so it really does need to be a directory. Dan/Dan, any reason we can't 'mkdir' this when libvirtd starts up?