If the BHYVE option is enabled in this port, then the configure check fails:
checking for bhyve... /usr/sbin/bhyve
checking for bhyvectl... /usr/sbin/bhyvectl
checking for bhyveload... /usr/sbin/bhyveload
test: /usr/sbin/bhyvectl: unexpected operator
Peter Krempa has submitted a patch that fixes the problem:
The patch is not in libvirt yet.
Until the patch is in, I suggest this patch to the configure script
of the port:
--- configure.orig 2014-06-07 18:27:57.809669553 -0700
+++ configure 2014-06-07 18:59:16.891541812 -0700
@@ -62467,7 +62467,7 @@
- if test -z "$BHYVE" || test -z "$BHYVECTL" \
+ if test -z "$BHYVE" || test -z "$BHYVECTL" || \
test -z "$BHYVELOAD" || test "$with_freebsd" = "no"; then
if test "$with_bhyve" = "check"; then
Over to maintainer.
Roman has a whole pile of fixes to the libvirt
port based on my feedback. See:
Can you incorporate those patches? They greatly improve the usability
of libvirt using bhyve.
As you have pointed out to me, I see in your latest commit to bump up the port
to 1.2.6 you have incorporated all of Roman's and my patches.
Can you incorporate the following small patch
to the virt-manager port:
It gets virt-manager to work with bhyve, which is kind of nice.
Roman has upstreamed another similar patch to get virt-manager to
work with bhyve. Unfortunately, this is not yet in a released
version of virt-manager. To get a newer virt-manager
in our ports system will pull in a lot of dependencies on GNOME3,
which we don't yet have in our ports tree, so it will
My patch is pretty small, but it gets bhyve working with virt-manager
which is super useful. If you could incorporate it, that would be great!