From owner-freebsd-virtualization@freebsd.org Wed Nov 4 15:23:43 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 ED53AA268F4; Wed, 4 Nov 2015 15:23:43 +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 971B41927; Wed, 4 Nov 2015 15:23:42 +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 tA4FNPRe049723 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 4 Nov 2015 15:23:28 GMT (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1446650611; bh=MGWWaxmBMCizwSoJYLq2PhDr5MC9xZ3szf7q6KKKU2w=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=dKJYWx7YgVocMaQvQzOQMOH4I/rYqRFdXM1ZC/aSeNWfeVIFIpM0bHzz589VWJfhq dpkiMzMqDSgXty48gnO9wChxmt162m++ht+Bh9ogvBJWTtup7cxGVnqzyrU6MFDEko khiZprWIQkYb7NAVtVZjmyriDJhpgRnv39LkEUy4= 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 15:23:19 +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 15:23:19 +0000 From: Matt Churchyard To: Larry Rosenman , Lars Engels CC: "owner-freebsd-virtualization@freebsd.org" , FreeBSD virtualization Subject: RE: C bhyve administration tool Thread-Topic: C bhyve administration tool Thread-Index: AQHRFoXM74mFoJK6AkqxRGclvqWnoJ6K6rKAgACvmZCAAFu4gIAAA3kw Date: Wed, 4 Nov 2015 15:23:18 +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 15:23:44 -0000 >> Hello! >>=20 >> 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. >> 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. >>=20 >> The effort stalled due to some high priority work that crept in. >> However, I am planning on restarting soon and wanted to check if=20 >> there was a need for something like this. I ran across Michael=20 >> Dexter's vmrc, and although its shell based, it does provide quite a=20 >> bit of features that we were looking for. There's also iohyve. And I=20 >> heard Peter and Neel are working on something as well. If there is=20 >> interest, this would be open sourced from the start. Or if there is=20 >> an existing effort that addresses these problems, I would love to=20 >> contribute to that project. >>=20 >> Thoughts, comments, concerns, please share. >>=20 >=20 >> vm-bhyve is most mature to this point IME, just don't use the ports=20 >> version. >=20 >> Adam >=20 > Thanks Adam :) >=20 > I could do with updating the port. Unfortunately this is my first=20 > porting experience so not exactly sure of the 'correct' channel to go=20 > through to get things updated. It took 2 months for my original port=20 > request to be addressed and I'm not sure re-opening that bug is the=20 > right way to do it. >=20 > If anyone uses the port, the error that gets printed when running 'vm=20 > init' can be completely ignored. It's just trying to load any existing=20 > virtual switches from the switch configuration file, and complaining=20 > that the switch configuration file doesn't exist. Apart from that and=20 > a few newer features/tweaks, I don't think there's anything=20 > particularly show-stopping about the current port/package if people=20 > prefer installing it that way to downloading from GitHub. >=20 > Of course it would still be interesting to see a "real" bhyve=20 > management tool (possibly even an official one) written in C. >=20 >to update an existing port, create a PR with the patch to update it, and t= hen wait. If a committer doesn't grab it within a reasonable time, post to= freebsd-ports to get their >attention. >Do run poudriere testport and provide the output. >--=20 >Larry Rosenman http://www.lerctr.org/~ler ------- >Hi Matt, >if you need someone to help you updating the port and get it committed, dr= op me a line and I'll help. >Lars Hi Lars, Larry Thanks both for your help. Once I'm sure I won't be making any changes 5 minutes after submitting it, = and don't have any other silly bugs scaring new users I will submit a PR. Matt