Date: Wed, 31 Dec 2014 17:56:58 +0000 From: Glen Barber <gjb@FreeBSD.org> To: Will Andrews <will@firepipe.net> Cc: hackers@freebsd.org, Ryan Kois <ryan.kois@gmail.com>, Alfred Perlstein <alfred@freebsd.org>, re@freebsd.org, Claudia Yadathi <yadathi@gmail.com> Subject: Re: How to make a FreeBSD vm in virtualbox. Message-ID: <20141231175658.GD75959@hub.FreeBSD.org> In-Reply-To: <CADBaqmhES1mFJ6iWjwRY=2Y9HJfDeJky%2BqwKmP9TeTdA6ufBfw@mail.gmail.com> 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> <CADBaqmhES1mFJ6iWjwRY=2Y9HJfDeJky%2BqwKmP9TeTdA6ufBfw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--pQhZXvAqiZgbeUkD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 31, 2014 at 10:48:20AM -0700, Will Andrews wrote: > On Wed, Dec 31, 2014 at 8:17 AM, Glen Barber <gjb@freebsd.org> wrote: > >> 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". >=20 > What about shipping Vagrant boxes instead? I've found those easy to > build automation on top of. >=20 I have not had luck with creating these. > > 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. > [...] > > I strongly oppose depending on building VirtualBox (which has > > implications of its own) for producing VM images, especially when the > > disk image can be created using base utilities alone. Given that, > > relying on a third-party utility is a step backwards. >=20 > Requiring that all tools used in the release process ship with the > base system means FreeBSD will never offer any first-party images for > use with third party tools, obstructing community development around > them. That would be a shame. >=20 My objection isn't necessarily that the tools are not in the base system, but something with such a large dependency footprint like VirtualBox is a non-ideal solution, when its alternative, mkimg(1) in this case, requires nothing extra. Prior to mkimg(1), qemu-img was used. And qemu has a significantly lower dependency footprint. Glen --pQhZXvAqiZgbeUkD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUpDjqAAoJEAMUWKVHj+KTSd0P/174RuAIBtH1vIdTyVNFzJ90 u1tbilYVOGqH7J5hwfy86GL5jFfIDZFtWms8OUkET2F/Yo+lfobeITRVCScw+6YU 66nTcIbXTzeO6z+9e/Z28NvvOLWJ1SY/xJiSDPJtjJnzvK3ybIqmU73vfM0dgu+/ +bXNbJaaDSRMQtG8tC+IntT1pTA0rwY9c9FKNnfRLSzZCm8A7C0rnVj1RkuPKDUO 0h3f+fw8hoUDajdXINWr4sHZssa24OOjVorelE3nPwXmIs0z8rk4Ks4aC1/Oaqry I62RseVHHhSrnL/lNOVELoYuMifxgE96VNCIIwH5aZeXa6ksJ2xz1lvToea4cNCU qNOSRy7bbcKSkQ7CV2VsETCc5sya8Ku6gBJSnM0KDsNvMuJ7bYJl4oUjMeVuBMom CKTduuj77uTriUWuQJB2Or3WimwZftar8dpOS5+6cSgJnAxInS8KAfaosp/PuiOO KwsyjwQA6GU+TooKnify/K7h6UW6UHrVswroY1emR0sJ8ndmFOaybeJxz2bGRP74 0XnkgRYKH1XjoskoUyzeI2/rgsq7WzG7ig+GapyufwnXLTpdCW/mYAvGrmWKvN67 nLWc0W66PbFaG0u1yd0gPTs3GLrf3bLkQid05l9vfk7bVsCFleMTCs11LS1fVM/W OwOoR/FytBxASJhLhnyw =u3M7 -----END PGP SIGNATURE----- --pQhZXvAqiZgbeUkD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141231175658.GD75959>