Date: Wed, 10 Jan 2018 21:34:13 -0800 From: Maxim Sobolev <sobomax@freebsd.org> To: stable@freebsd.org, freebsd-virtualization@freebsd.org Cc: mk@semihalf.com, mw@semihalf.com, FreeBSD Release Engineering Team <re@freebsd.org> Subject: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2 Message-ID: <CAH7qZftm=J9N4TqEsTY9fdxw0RSAy-Y7ROJ8_4r21x7xHu8xqw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, today we've migrated one of our FreeBSD EC2 r4.xlarge instances and painstakingly found that xn(4) interface is no longer provided by the Amazon "hardware". ena(4) seems to be now default for a newly created VMs, but it's not part of the GENERIC kernel. This could affect both new users trying to deploy stock FreeBSD on AWS, as well as existing users migrating their virtual assets running FreeBSD. I am not sure if there any technical reasons for not having it, but perhaps somebody needs to take a look to add it in there if there are none? -Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAH7qZftm=J9N4TqEsTY9fdxw0RSAy-Y7ROJ8_4r21x7xHu8xqw>