*-sock created as part of normal daemon startup?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



As noted in another thread, I've not had success with homebrew/Mac OSX's libvirt install.

On  Ubuntu  and CentOS virtual machines, installing "libvirt-daemon" and friends, I end up with various "-sock" files in /var/run/libvirt. This seems sensible.

After installing on MacOS X with homebrew

ls /usr/local/var/run/libvirt
hostdevmgr lockd qemu storage

so perhaps it isn't surprising that virsh -c vbox:/// fails.

Am I right in believing that the lack of -sock files means that the "brew services start libvirt" is either misconfigured or otherwise failing?


_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux