From owner-freebsd-arm@freebsd.org Tue Sep 8 13:16:20 2015 Return-Path: Delivered-To: freebsd-arm@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 659659CC542 for ; Tue, 8 Sep 2015 13:16:20 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FB791E80 for ; Tue, 8 Sep 2015 13:16:20 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id ACE2A961; Tue, 8 Sep 2015 09:16:12 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: bhyve/arm6/amd64 query From: Paul Mather In-Reply-To: <20150907150539.GA2959@potato.growveg.org> Date: Tue, 8 Sep 2015 09:16:12 -0400 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150907090541.GA54788@potato.growveg.org> <59F1B4A5-CD93-46D2-83D3-F0790CA2FA8E@gmail.com> <20150907150539.GA2959@potato.growveg.org> To: John X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Sep 2015 13:16:20 -0000 On Sep 7, 2015, at 11:05 AM, John = wrote: > On Mon, Sep 07, 2015 at 03:33:24PM +0300, Jukka Ukkonen wrote: >> AFAIK no. Bhyve is a plain hardware type of container, >> not a hardware emulator like qemu, nor a jail type >> container. >> You should be looking for qemu or something similar. >> Bhyve can be used for hosting other operating systems >> on the same type of HW as the vanilla system. >=20 > OK, thanks. You've saved me the work of trying then failing terribly = :D >=20 > It doesn't have to be hosted. The reason for me asking is, basically = can I take > the image and (as an image, not as an OS) can it be updated/recompiled = on different, > higher spec hardware, then returned to the Pi? >=20 > Hopefully I'm describing this right. You know on say amd64, an arm6 = system can be > cross-compiled as an installable system. That system is running. I = have updated it > (while installed on RPI2 hardware) and installed my configs, it works = great.=20 > Now I can unplug the microSD, dd it to a .img file, on another system, = to archive it.=20 > What I'm asking is, can I take that image while it's on the other = system, and=20 > interact with it to the extent that I can update/upgrade it? >=20 > *the other system is also freebsd11, but amd64* I do something similar to what you describe for my Raspberry Pi and = BeagleBone Black except I don't deal with it as a complete image. I = just work with the file systems on the SD card. I cross build the system on my FreeBSD/amd64 system using this guide: = https://wiki.freebsd.org/FreeBSD/arm/crossbuild. When I'm ready to = update the SD card on the Pi or BBB, I shut them down and then mount the = UFS2 file system on the FreeBSD/amd64 system. I run make installkernel = and installworld to the mounted SD card file system (mounted, e.g., at = /build/sys/bbb) and also run mergemaster (e.g., mergemaster -i -F -m = /build/src/head -A armv6 -D /build/sys/bbb). All this is really just = using the standard build tools, but with some extra option specified due = to the cross-build nature of the process. After unmounting the SD card, I put it back in the Pi or BBB and start = it up again. This method has worked without problems for me for a = while, and I can build a new kernel and world on my FreeBSD/amd64 system = in under 30 minutes, as opposed to the many many hours it takes to do it = natively on the Pi or BBB. Cheers, Paul.=