libvirt.conf has: uri_default = "bhyve:///system" # virsh capabilities error: failed to connect to the hypervisor error: no valid connection error: no connection driver available for bhyve:///system error: Failed to reconnect to the hypervisor # tail /usr/local/var/log/libvirt/libvirtd.log 2014-10-22 13:55:46.198+0000: 34468815872: error : virNetSocketReadWire:1477 : End of file while reading data: Input/output error 2014-10-22 13:55:46.199+0000: 34468820992: error : do_open:1166 : no connection driver available for bhyve:///system 2014-10-22 13:55:46.200+0000: 34468815872: error : virNetSocketReadWire:1477 : End of file while reading data: Input/output error 2014-10-22 13:56:13.023+0000: 34468820992: error : do_open:1166 : no connection driver available for bhyve:///system 2014-10-22 13:56:13.024+0000: 34468815872: error : virNetSocketReadWire:1477 : End of file while reading data: Input/output error 2014-10-22 13:56:13.025+0000: 34468819968: error : do_open:1166 : no connection driver available for bhyve:///system 2014-10-22 13:56:13.025+0000: 34468815872: error : virNetSocketReadWire:1477 : End of file while reading data: Input/output error
Auto-assigned to maintainer jgh@FreeBSD.org
I am guessing the absense of this driver is the problem: %%BHYVE%%lib/libvirt/connection-driver/libvirt_driver_bhyve.so pkg info --list libvirt shows that file is missing.
This is libvirt-1.2.6_3 / freebsd:11:x86:64.
I'm fixing it.
A commit references this bug: Author: bdrewery Date: Wed Oct 22 17:44:06 UTC 2014 New revision: 371364 URL: https://svnweb.freebsd.org/changeset/ports/371364 Log: - Fix support for BHYVE on head/amd64. Modifying OPTIONS_DEFAULT after including bsd.port.option.mk is not valid. Just check for existence of bhyve for now instead to determine default. PR: 194531 Reported by: Conrad Meyer Changes: head/devel/libvirt/Makefile