From owner-freebsd-virtualization@freebsd.org Wed Nov 4 10:19:06 2015 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76FE4A26170 for ; Wed, 4 Nov 2015 10:19:06 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DFD681783 for ; Wed, 4 Nov 2015 10:19:05 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id tA49lq8h038965 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 4 Nov 2015 09:47:53 GMT (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1446630477; bh=MzvnkW6AgvVPj+N76Hk1Kvhr3iiDaAMmtEGMOP9KgJA=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=vB3g7n0tUF9fP7HOXenYbtkYJ0mDxlUqxiBSfY2gSLk3OxWqfaj2QWCj1+P9vjJ6H heQZXlLSV8dGhcPETKcv/+H2RlopTRAts1W/4IwoWSB9kiv0ZSF99LtiJmH/R14xpx OC8a4Fs7BhN3tSjiY7BBG02K+IvrH86EPxs4vcVI= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 4 Nov 2015 09:47:47 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Wed, 4 Nov 2015 09:47:47 +0000 From: Matt Churchyard To: Adam Vande More , Shawn Debnath CC: FreeBSD virtualization Subject: RE: C bhyve administration tool Thread-Topic: C bhyve administration tool Thread-Index: AQHRFoXM74mFoJK6AkqxRGclvqWnoJ6K6rKAgACvmZA= Date: Wed, 4 Nov 2015 09:47:46 +0000 Message-ID: References: <20151103221930.GA50869@debnath.net> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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: Wed, 04 Nov 2015 10:19:06 -0000 > Hello! > > Couple months ago I started writing a bhyve management tool in C for=20 > our startup, in preparation for migration to FreeBSD for our servers.=20 > The goal was to be able to create, drop, and auto-start/stop/restart=20 > VMs, individually or all at once, and provide a plugin infrastructure=20 > to expose some metrics / errors for reporting and aggregation. More=20 > importantly it would detect errors/failures, report them and attempt=20 > to restart the VM per assigned policy. > > The effort stalled due to some high priority work that crept in. > However, I am planning on restarting soon and wanted to check if there=20 > was a need for something like this. I ran across Michael Dexter's=20 > vmrc, and although its shell based, it does provide quite a bit of=20 > features that we were looking for. There's also iohyve. And I heard=20 > Peter and Neel are working on something as well. If there is interest,=20 > this would be open sourced from the start. Or if there is an existing=20 > effort that addresses these problems, I would love to contribute to that = project. > > Thoughts, comments, concerns, please share. > >vm-bhyve is most mature to this point IME, just don't use the ports versio= n. > Adam Thanks Adam :) I could do with updating the port. Unfortunately this is my first porting e= xperience so not exactly sure of the 'correct' channel to go through to get= things updated. It took 2 months for my original port request to be addres= sed and I'm not sure re-opening that bug is the right way to do it. If anyone uses the port, the error that gets printed when running 'vm init'= can be completely ignored. It's just trying to load any existing virtual s= witches from the switch configuration file, and complaining that the switch= configuration file doesn't exist. Apart from that and a few newer features= /tweaks, I don't think there's anything particularly show-stopping about th= e current port/package if people prefer installing it that way to downloadi= ng from GitHub. Of course it would still be interesting to see a "real" bhyve management to= ol (possibly even an official one) written in C. Matt