From owner-freebsd-virtualization@freebsd.org Thu Jan 11 17:13:09 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E07AE6FEB3 for ; Thu, 11 Jan 2018 17:13:09 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6405A7AE54; Thu, 11 Jan 2018 17:13:09 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-75-82-192-14.socal.res.rr.com [75.82.192.14]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id db26cbf4 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 11 Jan 2018 09:12:43 -0800 (PST) Subject: Re: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2 To: Maxim Sobolev , freebsd-virtualization@freebsd.org References: From: Pete Wright Message-ID: <3b5baa95-e87e-a527-5917-777ba0d6bca4@nomadlogic.org> Date: Thu, 11 Jan 2018 09:13:06 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 17:13:09 -0000 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 pete@nomadlogic.org @nomadlogicLA