From owner-freebsd-virtualization@freebsd.org Thu Jan 11 18:14:57 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 4FDD2E73403 for ; Thu, 11 Jan 2018 18:14:57 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D90FF7DB6B for ; Thu, 11 Jan 2018 18:14:56 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-ua0-x231.google.com with SMTP id u2so2272001uad.13 for ; Thu, 11 Jan 2018 10:14:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jqJfOg58rw7rhTFeKY05rbE1k0eZ0Gyro8TkvGeT5Fs=; b=vuFVnvkW03dI1IQwm0VuSqR/Go9f/VJpzP5p8jBmsECAp6YV/9G4dIRxQeWkk/pxEX 65gW+x4oD9Dt+k6rqtI4aCXxAS55WygK4zKiYaJJijNN91wXLylNcl/khg1It1mIjfSm DBv/aS4c2PNhE/vojBjYcitMh1vFbyxeTDx65/YcYFuMggaNOFYgMOnMJpCjGsox6WGf e0fWxBAyMCkxbQ9caQv6OPksSCq6NRoTTkzwSrFIZ8eSENrgxFdUnie4N/SXvFWzlMmy A1T3KtkLUwuvMFwjZUYn6W/+4uQCfi6U4bIPGcD8SnUvhEOjvNXYYH0opWKdn85ZZ/Ya yuSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=jqJfOg58rw7rhTFeKY05rbE1k0eZ0Gyro8TkvGeT5Fs=; b=CgP302nzCK0vbavau3BrPwr48VGSp82xqLZBwo9W1peOEptRwodExEblOGEKGxYBbt VdBiWVug26v6LsMYyOSqozu/sDia9jdGX+QjuaoBnYXPv64l0fBhT9aZLpT6KKEnXsKA kbjKVhRueFbnIT4zMCFQ6JAVP+jALfXfzS0XXYORiljdE/Fyq4y0SfiMlsydK0nDI0uu 8KMdvgcURdnofG/LgLj9+WdNEMxl6BE8c8i66vFG5fv12NLjMUaZ1hVV7/gWGCgMgiOC AyZUmgrLIkzRUBBQ5ebdtXxHCFDTumIENSFFdE7upoZ8646AIARn+scSjJ4Y9zPSLe0b wSvA== X-Gm-Message-State: AKwxytersvDo/pRnhhtym+iWxm6CLD4HASV38rTWxwE8HjczSXsMioE2 KCy3HfDTM2Bx3HOEioOf9LzrKc6yL36NhcUQFoberw== X-Google-Smtp-Source: ACJfBosfl4e69640pT+TyOngQYHpwAKGflMOTHFcQkFqE38UT/GMoc+/BVk5BWFRDYbqPEEEctjZHAjggeLnyRX73hI= X-Received: by 10.176.77.84 with SMTP id k20mr1392165uag.5.1515694495783; Thu, 11 Jan 2018 10:14:55 -0800 (PST) MIME-Version: 1.0 Sender: sobomax@sippysoft.com Received: by 10.159.41.102 with HTTP; Thu, 11 Jan 2018 10:14:55 -0800 (PST) In-Reply-To: <3b5baa95-e87e-a527-5917-777ba0d6bca4@nomadlogic.org> References: <3b5baa95-e87e-a527-5917-777ba0d6bca4@nomadlogic.org> From: Maxim Sobolev Date: Thu, 11 Jan 2018 10:14:55 -0800 X-Google-Sender-Auth: JcRsnVPBohstTlsDMk7pwnuVO3s Message-ID: Subject: Re: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2 To: Pete Wright Cc: freebsd-virtualization@freebsd.org, mk@semihalf.com, Marcin Wojtas Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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 18:14:57 -0000 Well, that might work, but I am curious why do we have all other network 40 or so drivers in the GENERIC but not this one. Considering significant portion of FreeBSD systems deployed these days are going to be running on the cloud this makes no sense to me. Is there some policy out there which governs such decisions? At the very least we need some kind of entry into UPDATING, IMHO. -Max On Thu, Jan 11, 2018 at 9:13 AM, Pete Wright wrote: > > > 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 > >