Hi Craig,
I've given it a try and its looking good.
 I already had some bhyve vms i wanted to import rather than creating
new. This worked fine.
I didnt ever get the default network which isnt an issue as its the
first thing I undefine on any KVM server I've use libvirt on.
Also I created the bridges myself as  I was unsure how libvirt was
supposed to do this and I've always created them manually for linux
libvirt/kvm instances, just letting libvirt create the vnet interfaces.
I'm using zvols rather than file backed but thats not causing any issues.

I'd suggest the port have a pkg-msg to suggest you add
uri_default = "bhyve:///system"
to /usr/local/etc/libvirt/libvirt.conf
so you can simply use
virsh list
etc instead of needing to specify the uri each time.


Thanks for all the work on this.
Vince


On 18/06/2014 19:29, Craig Rodrigues wrote:
> Hi,
>
> I've had some success with getting libvirt and bhyve to work.
>
> I wrote up a list of the steps that I followed here:
>
> http://people.freebsd.org/~rodrigc/libvirt-bhyve/libvirt-bhyve.html
>
> If anyone is interested, please try it out, and provide feedback to this
> list.  It would be great to get more testers.
>
> Roman, when do you think you will be able to commit all your latest
> fixes into the devel/libvirt port Makefile?  It would greatly increase
> the usability of the port.  Thanks for doing all the work to add bhyve
> support to libvirt!!
>
> --
> Craig
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"
>

_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to