From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 31 18:20:17 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 834CA2DE; Wed, 31 Dec 2014 18:20:17 +0000 (UTC) Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F4A2386B; Wed, 31 Dec 2014 18:20:17 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id q58so2730772wes.12; Wed, 31 Dec 2014 10:20:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=bBoJwZUeNlIRyj2d2yBN5xUQ4GXvie5dm9xygbzzCmc=; b=RULG21tTh5mTlM5RtghLEIuykrUfVOiYJQ9o968HUZM9KHqH36+EjL9pQxJieXp2D7 x/z2CYVanRfOqT/9XO6MgndgkgwiHZU3D9zWFQRtHLMozEfn9qrXoBBypbw5LvV2a7OO 0Y8BuS0JtbKNTw6EcS/JoFrDjiLlB9lvvDUo9mlxd7Qj94yXS4R6keTHFL1cL0TzZJRk M+TcfRxB3sXN45MCCJr4x7Sfo1tTWXUarnPSqPblQtCbHdj3ttKEJW8TG+LD/1TCLFFb W1aZtkNKLmngksQfpIvD2JeglEOpz4UNLOtpGHOaGDLzLiDDr7nApvUP/P6NZFK1hj61 0nhw== MIME-Version: 1.0 X-Received: by 10.180.14.136 with SMTP id p8mr80339583wic.20.1420050015389; Wed, 31 Dec 2014 10:20:15 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Wed, 31 Dec 2014 10:20:15 -0800 (PST) In-Reply-To: <54A43D56.4030306@freebsd.org> 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> <54A43D56.4030306@freebsd.org> Date: Wed, 31 Dec 2014 10:20:15 -0800 X-Google-Sender-Auth: jCRBlf2IC3ueqfX3ZUEpN_Vy998 Message-ID: Subject: Re: How to make a FreeBSD vm in virtualbox. From: Adrian Chadd To: Allan Jude Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" 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:20:17 -0000 On 31 December 2014 at 10:15, Allan Jude wrote: > 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 release >>>>>> process. >>>>>> >>>>> >>>>> We already provide VMDK images. There is nothing, that I can see, that >>>>> is different from how I've been testing the various images. Creating >>>>> a new VM and attaching the VMDK to the disk controller is the intended >>>>> 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 Marcel >>> added VMDK support to mkimg(1) - all the components to create the >>> formatted disk image exist in the base system. >>> >> >> Long ago I had created the quick and really dirty: >> https://people.freebsd.org/~bapt/vmdkimage-srcs/ >> >> This created ova files ready to be used in virtualbox (I had problem with vmware >> I don't remember why) >> >> basically an ova file is a tar file in a given order with a template >> (FreeBSD.ovf) and a manifest with checksums) >> >> This is really easy to produce and I agree it would be nice if we could produce >> one. >> >> The matter for having something that worked both in vbox and vmware was playing >> with the disk controler. >> >> 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) >> >> Now that we have mkimg that should be rather easy to create an ova generator at >> least for virtualbox (vmware compatible might be more tricky) >> >> The interesting part is that the ova format is normalized and used by lots of >> the virtualisation tools out there >> >> Best regards, >> Bapt >> > > 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 Course not, but then you have two problems - .xml and "no tool to generate / modify the config programatically." -adrian