From owner-freebsd-virtualization@FreeBSD.ORG Fri Jun 20 12:56:20 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F6BCCCF; Fri, 20 Jun 2014 12:56:20 +0000 (UTC) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "unsane.co.uk", Issuer "unsane.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EC9B32E8D; Fri, 20 Jun 2014 12:56:19 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) (authenticated bits=0) by unsane.co.uk (8.14.8/8.14.8) with ESMTP id s5KCuGoW060936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 20 Jun 2014 13:56:17 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <53A42F70.7040707@unsane.co.uk> Date: Fri, 20 Jun 2014 13:56:16 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Craig Rodrigues , "freebsd-virtualization@freebsd.org" Subject: Re: Request for Testers: libvirt and bhyve References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Roman Bogorodskiy X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2014 12:56:20 -0000 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-unsubscribe@freebsd.org" >