Date: Fri, 3 May 2024 10:02:39 -0700 From: John Baldwin <jhb@FreeBSD.org> To: Gleb Smirnoff <glebius@freebsd.org>, Mark Johnston <markj@freebsd.org> Cc: src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: aa34b1d20e44 - main - vmrun.sh: Add arm64 support Message-ID: <f0b0ccde-d4e6-455f-aa81-f04e7314d218@FreeBSD.org> In-Reply-To: <ZjT7jvV05MiTtVOv@cell.glebi.us> References: <202405011301.441D1xEc000624@gitrepo.freebsd.org> <ZjT7jvV05MiTtVOv@cell.glebi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/3/24 7:58 AM, Gleb Smirnoff wrote: > On Wed, May 01, 2024 at 01:01:59PM +0000, Mark Johnston wrote: > M> vmrun.sh: Add arm64 support > M> > M> For now, we enumerate disk devices before network devices. This is to > M> work around a problem wherein u-boot remaps BARs during boot in a way > M> that bhyve does not handle. Some discussion and experiments suggest > M> that this can be handled by having bhyve not map BARs during boot on > M> arm64; until a solution is implemented, however, this workaround is > M> sufficient for simple usage and doesn't have any real downsides. > M> > M> The console and bootrom are specified slightly differently versus amd64, > M> and a few of vmrun.sh's command-line options are amd64-only. > M> > M> Reviewed by: corvink, jhb > M> Sponsored by: Innovate UK > M> Differential Revision: https://reviews.freebsd.org/D44933 > > The share/examples/bhyve/vmrun.sh is not really an example, but a good > standalone tool. I use it all the time without any modification, and I > guess many other people do, too. > > Maybe time to move it to some path that is in the default $PATH? I really think we should instead be building a tool like vm-bhyve from ports, either by importing that directly, or perhaps rewriting it in lua and having that eventually replace vmrun.sh. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f0b0ccde-d4e6-455f-aa81-f04e7314d218>