[libvirt-users] error : virPidFileAcquirePath:345 : Failed to acquire pid file '/home/corey/.libvirt/libvirtd.pid': Resource temporarily unavailable

Daniel P. Berrange berrange at redhat.com
Wed Oct 31 15:00:25 UTC 2012

On Wed, Oct 31, 2012 at 08:51:04AM -0600, Eric Blake wrote:
> On 10/31/2012 02:06 AM, 何鑫 wrote:
> [please don't top-post on technical lists]
> > Thanks for your reply! I have solved the problem.
> > Could you please give me some tips for another question?
> > When I start libvirtd using "libvirtd -d", the process could be found by "ps". But I also can't search "libvirt-sock", because it fails to create after libvirtd starting. The configuration file isn't existed in default paths, as well as Sockets. When and how could both files create? 
> libvirtd creates libvirt-sock in a directory selected by the arguments
> you passed to configure.  The configuration file is optional (it is up
> to you to create it if you want it - libvirt merely reads it if it exists).
> >  Configuration file (unless overridden by -f):      $HOME/.libvirt/libvirtd.conf
> >     Sockets:      $HOME/.libvirt/libvirt-sock (in UNIX abstract namespace)
> Hmm - I wonder if we have a flaw in our documentation - the name
> $HOME/.libvirt/libvirt-sock implies that the socket is NOT in the
> abstract namespace; I know we recently changed where qemu:///session
> looks for its socket, but I don't remember if the change was from
> abstract to named, or from named to abstract.

We stopped using the abstract namespace, since it is not supported on
several UNIX, and also didn't let you connect remotely with the ssh/nc

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

More information about the libvirt-users mailing list