after a reboot into recovery mode, csrutil enable --without dtrace
(ignoring warnings about how horribly unsupported this is). This eliminates
the dtrace errors, but virsh remains ill. Clue bats appreciated!
Last login: Mon Jan 7 12:31:39 on console
/Users/AB84394>sudo dtruss -fn virsh
PID/THRD
export LIBVIRT_DEBUG=2
Produces the attached
2019-01-08 20:34:52.030+: 4433659328: info : libvirt version: 4.10.0
2019-01-08 20:34:52.030+: 4433659328: info : hostname: khb-X1078182.local
2019-01-08 20:34:52.030+: 4433659328: info : virEventPollAddHandle:137 :
EVENT_POLL_ADD_HANDL
Borrowed an old lab mac running 10.13.6 installed brew from scratch,
installed libvirt ... same failure. Advise about how to debug would be
appreciated!
*➜ * virsh -c vbox:///session list
error: failed to connect to the hypervisor
error: internal error: Failed to create vbox driver object.
Mac OS X 10.14.2
VirtualBox 5.2.22 and 6.0.0
libvirt installed via homebrew
virsh -V
Virsh command line tool of libvirt 4.10.0
See web site at https://libvirt.org/
Compiled with support for:
Hypervisors: QEMU/KVM VMware VirtualBox ESX Test
Networking: Remote Bridging
Storage: Dir
Misce
