From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 31 03:42:37 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 715ADABE; Wed, 31 Dec 2014 03:42:37 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 60E41181B; Wed, 31 Dec 2014 03:42:37 +0000 (UTC) Received: from [10.0.1.20] (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 1A9A2341F854; Tue, 30 Dec 2014 19:42:37 -0800 (PST) From: Alfred Perlstein Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: How to make a FreeBSD vm in virtualbox. Date: Tue, 30 Dec 2014 19:42:36 -0800 Message-Id: <13C55A7B-4010-40FA-901B-DF8ED6BADD87@freebsd.org> To: re@freebsd.org, hackers@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) Cc: Ryan Kois , Claudia Yadathi X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2014 03:42:37 -0000 Hello Release engineering team & hackers, Ryan (cc'd) did some work on the recent FreeBSD vms that were released. Ryan is working at Norse with us and using FreeBSD now. His background = is backend development in io.js, node.js and php on Linux. He's now trying to get io.js working on FreeBSD. In doing so he wanted to setup a VM, so he downloaded the vmdk and = created a blog post on what was needed to be done in order to get it = working under virtualbox. That blog is here:=20 = http://blog.kidicarus.cool/blog/2014/12/24/freebsd-guest-on-mac-osx-host-v= ia-virtualbox/ After he linked it to me, I decided that it would make sense if this was = scripted and would really make sense as part of the release process. I've written a script that will make a .ova that you can one-click = import into Virtualbox (and I think Fusion as well) here: https://gist.github.com/splbio/84bd4d2122782e99fc5c What is the best way to get this made into part of the release process = so that we can get .ovas shipped as well. Is there a starting point for integration with the release building = process? One final question, is there a possibility we could add some changes to = the image so that it auto-dhcp's an address? Most people who just = download the image won't know to "dhclient em0" or even what an "em0" = is. =20 Funny fact about "em0": everyone I know who's not a FreeBSD person calls = it "Emo" like the "emo kids" with the funny hairstyles. Here is an = image gallery of what I'm talking about: = https://www.google.com/search?q=3Demo&es_sm=3D91&source=3Dlnms&tbm=3Disch Anyhow, I was wondering what you guys think of adding some hook to the = release process to inject a rc.conf entry to make "ifconfig_em0=3D'DHCP'" = as part of the build? Or is there a better way? Suggestions on a way = forward for this? Alfred Perlstein=20 Sr. Director, Appliance & Kernel Engineering=20 Norse=20 cell: 415 312 3931=20=