Date: Wed, 16 Oct 2019 20:27:54 +0000 From: Colin Percival <cperciva@tarsnap.com> To: Michael Tuexen <Michael.Tuexen@macmic.franken.de> Cc: freebsd-arm@freebsd.org Subject: Re: EC2 ARM64 "bare metal" instances Message-ID: <0100016dd6416a96-9fd7b02a-7ad0-4713-aca2-9df99123f6fe-000000@email.amazonses.com> In-Reply-To: <B39F25E7-39F0-4979-93F7-4513404E9DA7@macmic.franken.de> References: <0100016dd57b89f3-034edaf3-4ae3-46f6-96ad-a3f0cf202c05-000000@email.amazonses.com> <B39F25E7-39F0-4979-93F7-4513404E9DA7@macmic.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-10-16 11:25, Michael Tuexen wrote: >> On 16. Oct 2019, at 18:51, Colin Percival <cperciva@tarsnap.com> wrote: >> FreeBSD does not currently boot on Amazon's recently released "bare metal" >> ARM64 instances. It might be useful to get these working, since they're >> reasonably powered hardware (16 cores, 32 GB RAM) and should be able to run >> bhyve (that's the "bare metal" part). > Not sure we have bhyve support for arm64 in tree right now... Maybe not, but I'm pretty sure someone was working on it? >> Right now the boot is failing because FreeBSD is not finding the disk (or >> the network adapter, for that matter): > Isn't your device similar to > https://dmesgd.nycbug.org/index.cgi?do=view&id=4813 Very similar, yes. That link concerns the same physical hardware, but running inside Amazon's KVM-like hypervisor. When running on the "bare metal" version of the EC2 instance we need to set up PCI controllers etc. ourselves since we don't have a hypervisor doing it for us. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0100016dd6416a96-9fd7b02a-7ad0-4713-aca2-9df99123f6fe-000000>