Date: Mon, 27 May 2019 10:26:48 +0300 From: Mihai Carabas <mihai.carabas@gmail.com> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: virtualization@freebsd.org Subject: Re: bhyve/arm64 status Message-ID: <CANg1yUtjSEUdETA1gfiYU3S1AgcuO3nLYf%2Bns5EG=3XjneJLeA@mail.gmail.com> In-Reply-To: <20190527013609.dl6zup3rinzh3tw4@mutt-hbsd> References: <20190527013609.dl6zup3rinzh3tw4@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, There is no bhyve-arm/arm64 in current. All the code is on our repo here [1], but has an old HEAD. We did a rebase last week but we did not tested [2]. Currently the code is not mergeable as bhyve does not have a structure of machine dependent/independent code and creating such a structure would take some time. We talked with John Baldwin at BSDCan to find a easiest way to merge arm/arm64. In the next months we hope we will find the suitable solution to get the code into current. Thank you, Mihai [1] https://github.com/FreeBSD-UPB/freebsd/commits/projects/bhyvearm64 [2] https://github.com/FreeBSD-UPB/freebsd/commits/projects/bhyvearm64-refactor On Mon, May 27, 2019 at 4:37 AM Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > > Hey all, > > I'm trying to figure out the state of bhyve on arm64 in 13-current. I > have two SoftIron OverDrive 1000s, a bajillion RPI3s, a Pine64, > Rock64, and PineBook, and a ThunderX2. Punish me. > > Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > Tor-ified Signal: +1 443-546-8752 > Tor+XMPP+OTR: lattera@is.a.hacker.sx > GPG Key ID: 0xFF2E67A277F8E1FA > GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANg1yUtjSEUdETA1gfiYU3S1AgcuO3nLYf%2Bns5EG=3XjneJLeA>