From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 31 18:15:50 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E2C7E5 for ; Wed, 31 Dec 2014 18:15:50 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 0C8943816 for ; Wed, 31 Dec 2014 18:15:49 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 6CB1B8A371 for ; Wed, 31 Dec 2014 18:15:43 +0000 (UTC) Message-ID: <54A43D56.4030306@freebsd.org> Date: Wed, 31 Dec 2014 13:15:50 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: How to make a FreeBSD vm in virtualbox. References: <13C55A7B-4010-40FA-901B-DF8ED6BADD87@freebsd.org> <20141231042455.GB53230@hub.FreeBSD.org> <24520431-8E2A-4D70-BD2D-D8D76A98C762@freebsd.org> <20141231151723.GA75959@hub.FreeBSD.org> <20141231180639.GE43180@ivaldir.etoilebsd.net> In-Reply-To: <20141231180639.GE43180@ivaldir.etoilebsd.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qoSnanvcoASsirU71pedhm9tuV64PLFJf" 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 18:15:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qoSnanvcoASsirU71pedhm9tuV64PLFJf Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-12-31 13:06, Baptiste Daroussin wrote: > On Wed, Dec 31, 2014 at 03:17:23PM +0000, Glen Barber wrote: >> On Tue, Dec 30, 2014 at 10:04:38PM -0800, Alfred Perlstein wrote: >>> >>> On Dec 30, 2014, at 8:24 PM, Glen Barber wrote: >>> >>>> On Tue, Dec 30, 2014 at 07:42:36PM -0800, Alfred Perlstein wrote: >>>>> 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 releas= e >>>>> process. >>>>> >>>> >>>> We already provide VMDK images. There is nothing, that I can see, t= hat >>>> is different from how I've been testing the various images. Creatin= g >>>> a new VM and attaching the VMDK to the disk controller is the intend= ed >>>> workflow. >>> >>> The difference is that with a vmdk you must get the exact >>> combinations of items correct or you will wind up with a FreeBSD >>> instance that will not boot. With the ova, you just run a single >>> command "VBoxManage FreeBSD.ova" and stuff "just works", or you can >>> even just double click on the downloaded file from within your OS >>> X / Windows/ whatever host and it "just works". >>> >>> >>>> >>>>> 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 >>>>> >>>> >>>> Can you send the script as an attachment? >>> >>> Uh sure. It's attached. >>> >> >> Your script relies on VirtualBox being installed on the build machine,= >> which I do not like. This is one of the major reasons I'm happy Marce= l >> added VMDK support to mkimg(1) - all the components to create the >> formatted disk image exist in the base system. >> >=20 > Long ago I had created the quick and really dirty: > https://people.freebsd.org/~bapt/vmdkimage-srcs/ >=20 > This created ova files ready to be used in virtualbox (I had problem wi= th vmware > I don't remember why) >=20 > basically an ova file is a tar file in a given order with a template > (FreeBSD.ovf) and a manifest with checksums) >=20 > This is really easy to produce and I agree it would be nice if we could= produce > one. >=20 > The matter for having something that worked both in vbox and vmware was= playing > with the disk controler. >=20 > What I did back in the time was generating an ova from vbox extracting = the .ovf > reducing to the minimum required the final ovf and ask people to import= in in > vmware (I do not have access to any vmware) >=20 > Now that we have mkimg that should be rather easy to create an ova gene= rator at > least for virtualbox (vmware compatible might be more tricky) >=20 > The interesting part is that the ova format is normalized and used by l= ots of > the virtualisation tools out there >=20 > Best regards, > Bapt >=20 I was going to say, I thought a .ova file was just a .tar of the .vmdk and a .xml config file It doesn't seem like virtualbox would be required if the .xml file was generated and then checked into the tree --=20 Allan Jude --qoSnanvcoASsirU71pedhm9tuV64PLFJf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUpD1ZAAoJEJrBFpNRJZKf1f4QAMSAsmS0FJE8fEzVvcNelMS0 mW6MJMPBj9L6ZCjMjNXyMipPrQrJUOW+jfMPwKAnVWAwyuqJvZxyYVUEz4UjZtGx A3SjZuh1RolszvQ6gxUvVG72R8V2edBzEiQGRYK2UhDJjwK/WmV2SxS+s4s0siIC p4bdZbNNadw/+mH56abO+Tg8tK8QacU5WZGKQkjRVJE8bA/98cmy59olP00vACEu 8Of/f5nfTXMrwtAMcrRlKwHDxLO7EbE3Qd5Bpzcjulrs3aKUWgQN1/eooquSELWG /OiawqYtY9xFi0Ao7t2J/JHM6xyhi/ffZprj8eUi5RZL9kzzgoMJwIN0GXz2CJ2O pSDzsr8jvx+4qVEPgzFrEIqjW5p1aoYZlIi9GFg2mFFM6SF+K0JShbPI9ddSsmLY xF4NKCBZH0cUTv6sMQ//MadpHhgtNyMsiIwuLcqFeZGqyjOD7JoCvlsb7eW+vU4I ZFIbXzE0ORvDS/V8dJBULZbkEdjXWzrn/KoBA4kG9iE2tfjjZtVj1/wDepHTHLlM YvoMSP/7KMn/lj9b3JUiM7Te8sq4Uxz9RIW+wfyYmNYcUtrv+7fVDNu7wKEAzIw0 ljqnMVR04LRlCzFEPOg4Rb4+Wjra3v9htrEzjyXtXjA+2aX9z9aVZzu4ubEhizSA oy5JJrbvk55C8hWxfk5V =W2QX -----END PGP SIGNATURE----- --qoSnanvcoASsirU71pedhm9tuV64PLFJf--