On 01/10/2018 21:34, Maxim Sobolev wrote:
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?
(removing cross-posting as I believe this is relevant to the virtualization list mostly.)
if_ena.ko is shipped as a kernel module on 11.1 on my end - would using configinit to append if_ena.ko to kld_list or loader.conf might be a decent workaround? i would have assumed it would have been loaded at boot time if the device was detected, but i've never tested out instances that only support the ena(4) adapter.
-p -- Pete Wright p...@nomadlogic.org @nomadlogicLA _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
