On Mon, May 17, 2021 at 12:28:39AM +0300, Ilya Voronin wrote:
> I was able to fix boot error on t3a (AMD EPYC based) instances (kernel:
> protection fault trap at lapic_set_lvt:rdmsr) with this patch (tested
> against 6.9):
>
> Index: arch/amd64/amd64/lapic.c
>
I was able to fix boot error on t3a (AMD EPYC based) instances (kernel:
protection fault trap at lapic_set_lvt:rdmsr) with this patch (tested
against 6.9):
Index: arch/amd64/amd64/lapic.c
===
RCS file: /cvs/src/sys/arch/amd64/amd64
OK, looks like ENA (Elastic Network Adapter) is the main show stopper here,
There is a glimpse of optimism here, FreeBSD port of ENA driver is
already out there:
https://github.com/amzn/amzn-drivers/tree/master/kernel/fbsd/ena
I'm trying to catch the AMD-specific crash logs from t3a-type instanc
Hi All!
Not so long time ago I've got the challenge to fire up OpenBSD instance
in AWS. It was almost out-of-the-box successful with just a few manual
post-configs... However, with recently introduced "Nitro" hypervisor
(heavily streamlined KVM) old methods of hacking OpenBSD into the Amazon
Cloud
4 matches
Mail list logo