OK, thanks to Mike and Antoine! I tried with t2 instances (current generation - the only choice present), yet still no dice. Perhaps, the issue is with how I created the image. I used qemu, created qcow2, installed openbsd, converted qcow2 to raw and then with vmdktool converted raw to vmdk. AWS recognized vmdk with out any issue and booted it. But no xnf0 interfaces were detected.
On Thursday, October 26, 2023 at 04:47:18 p.m. GMT+9, Antoine Jacoutot <ajacou...@bsdfrog.org> wrote: On Tue, Oct 24, 2023 at 10:40:34PM +0000, All wrote: > Hi, > > There was a time when we could run OpenBSD on AWS. > Antoine Jacoutot did a great work to make that possible. > These days, xnf0 interface is not being initialized. Xen is being > identified as Xen 4.11 (12?) but no xnf interfaces are sowing up > after boot. NetBSD has xennet0 being initiated and FreeBSD (I guess) xnb. > > Did anyone else faced similar problem? Actually Mike Belopuhov (mikeb@) did all the work, I just assembled things. For me me it still works with old generation of ec2 instances (e.g. t2). New generations are using KVM but we are missing the ENA driver for network (and maybe other things). Cheers! -- Antoine
