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 instances to post them here. On 06.10.20 07:50, Kirill Peskov wrote: > 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 seem not to be working, due to not yet fully known list of > reasons, but some of the key differences between "t2" and "t3" > generations are obvious, t3 has new components: > > Root disk: NVMe root disk > NIC: Elastic Network Adapter (Amazon ENA) > > In addition, AWS has a bit cheaper line of instances, AMD-based "t3a". > > So far, from the instance startup logs I can see that NVMe device is > detected by OpenBSD kernel, but looks like OS is unable to find root > partition on the drive. AMD instance crashes with kernel fault on very > early stage. > > Has anyone tried the same? Any success? > > > Cheers, > > Kirill
smime.p7s
Description: S/MIME Cryptographic Signature
