Mojave allergic to libvirt?

[KeithBierman]

MacOS 10.14.2 virt-manager --version 2.0.0 virsh --version 4.10.0

brew install libvirt libvirt-glib virt-manager virt-viewer . # which memory says used to work
...all the usual brew install messages appear sane
brew services start libvirt

virsh -c vbox:///session list                               
error: failed to connect to the hypervisor
error: internal error: unable to initialize VirtualBox driver API

Tried removing everything and reinstalling ... no change. Virt-manager comes up, but seems unhappy

The libvirtd service does not appear to be installed. Install and run the libvirtd service to manage virtualization on this host.
Could not detect a default hypervisor. Make sure the appropriate qemu/kvm virtualization packages are installed to manage virtualization on this host.
A virtualization connection can be manually added via File->Add Connection

Note that VirtualBox is installed (6.0). Clicking on "File" doesn't bring up the add connection subpage.

[jeffreywildman]

VirtualBox 6.0 was just recently released, libvirt does not appear to support it yet. Perhaps roll back to 5.x or submit the issue upstream?

https://libvirt.org/git/?p=libvirt.git;a=tree;f=src/vbox;hb=HEAD

[KeithBierman]

On Jan 8, 2019, at 8:01 PM, Jeffrey Wildman notifications@github.com wrote:

VirtualBox 6.0 was just recently released, libvirt does not appear to support it yet. Perhaps roll back to 5.x or submit the issue upstream?

Same behavior observed with 5.2.22 ; at this point I’m clue impaired as to whether it’s a stupid pilot error, a brew formula, or a libvirt error. I’ve removed your tap/cask and the virt-manager/viewer and ensured a clean report from “brew doctor” with the failure persisting :(

https://libvirt.org/git/?p=libvirt.git;a=tree;f=src/vbox;hb=HEAD

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[KeithBierman]

On Tue, Jan 8, 2019 at 9:13 PM Keith Bierman khbkhb@gmail.com wrote:

On Jan 8, 2019, at 8:01 PM, Jeffrey Wildman notifications@github.com wrote:

VirtualBox 6.0 was just recently released, libvirt does not appear to support it yet. Perhaps roll back to 5.x or submit the issue upstream https://libvirt.org/bugs.html?

Same behavior observed with 5.2.22 ; at this point I’m clue impaired as to whether it’s a stupid pilot error, a brew formula, or a libvirt error. I’ve removed your tap/cask and the virt-manager/viewer and ensured a clean report from “brew doctor” with the failure persisting :(

Humm, after several uninstall/reinstalls, I've found that the consistent error is now

/Users/AB84394/LIBvirtdebugging/new>virsh -c vbox:///

error: failed to connect to the hypervisor

error: Failed to connect socket to '/usr/local/var/run/libvirt/libvirt-sock': No such file or directory

Which matches one of the libvirt project's faqs about a build error. Brew doctor is clean, brew produces no error messages and brew reports that the service is running ... so perhaps this IS properly a brew/formula issue ...

Error: unable to connect to '/var/run/libvirt/libvirt-sock'

This is usually caused by one of the following:

• libvirtd is not running. On fedora systems, this can be fixed with:

service libvirtd restart

• Or you could run it like this

/etc/init.d/libvirtd restart

• You manually installed from source, and something is screwy. virsh may be looking for the socket in '/usr/local/var', but your installed libvirtd isn't creating it correctly.

[Rishats]

Same problem.

[jeffreywildman]

It looks like the issue has been isolated to virsh/libvirt whose formula is provided by homebrew-core. I suggest opening an issue at https://github.com/Homebrew/homebrew-core for greater visibility.

[jeffreywildman]

Closing due to inactivity + there are better venues for this issue.