From owner-freebsd-stable@freebsd.org Thu Jan 11 05:34:15 2018 Return-Path: Delivered-To: freebsd-stable@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 94001E6E76B for ; Thu, 11 Jan 2018 05:34:15 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6E3FC7F83A for ; Thu, 11 Jan 2018 05:34:15 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6DA21E6E768; Thu, 11 Jan 2018 05:34:15 +0000 (UTC) Delivered-To: stable@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 6D4CAE6E765 for ; Thu, 11 Jan 2018 05:34:15 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::22c]) (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 3E9917F838 for ; Thu, 11 Jan 2018 05:34:15 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-ua0-x22c.google.com with SMTP id e19so895203uam.6 for ; Wed, 10 Jan 2018 21:34:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to:cc; bh=4OBAemUci7kUGe9nTz1NHCr6wlESxpyKXIB8HTypPxg=; b=dgxFPd3nz8+foMs7DXIsD0fCvgHa5u374bTai3K/zy6j7Jm0YJD/aQmm+zq7kw/GHM D3e7MZ/OFIZRYzFyrJFR2r06LDZm1XZyX16Z4m8PYprdHTkCiC/Nr/AxVkdVQcuD2iFd bGqKDuE6oatPCKAee/ZU47R7qEc90MkqLUxuDB09Rz2X+anQBUJHAUFbdy57aGlOYcOb RY0alorocneQl+k6hqlFHv+9fCU5xA5bQnsY2l5ksJ8zt0N2MfcdpUrt6lSPvU0sPuSQ GPATvuG2tZ/uLRwoPYlWUaORxaflH7dpdeG6CL3avvAqV4CVKozYdC2Ckik2/t1CubI0 gqoA== 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:from:date:message-id:subject :to:cc; bh=4OBAemUci7kUGe9nTz1NHCr6wlESxpyKXIB8HTypPxg=; b=pjLusEYrkb2OQh1EznX1l4lZN/Y6kngDS8BeNqBK84pTtwroehyoCcfxG9n+CZenWu WBRBn2PPX4J4wgrP8r2QbM2Vw4Lovq+O9/vuil0ax152vbuG+yjNjQ66eSjgN+aK9DUY wjjpHw+ozQjVh/bjvrhdghdWiKzEVRvMy7rQ2D6Ye+lUSqfHF35Wf64lHUCCDi+KbHHV WRYlDmRl06648ggXsmWtD7QtgksMeaBpZX9vOuRPqoFa8AbOe+HVdKM14n4rNro5kdsj zBbGm26zt8un8yL3f9zqFJIwDWbLRBb0ptzajrG9SsO9WsnyP+pgf85bfKMgGRqUYlxx Rs2A== X-Gm-Message-State: AKwxytegxv9wynwHl3QZ0yQ95L2G9OY8xg77w37pWnRHfiTRgpTakGbs jjroshQNbKi9HERLAppHTtv+aeBl77/qyLoNk6Hshg== X-Google-Smtp-Source: ACJfBotTrDmnChhd29LvcKuG3BO4tPdnjwJ31jF1UDqzwckdXZZ+9BxPmAtzbpFangUKTH9pQZrr25ig1HJuu2i2Hck= X-Received: by 10.176.83.66 with SMTP id y2mr18755499uay.121.1515648853871; Wed, 10 Jan 2018 21:34:13 -0800 (PST) MIME-Version: 1.0 Sender: sobomax@sippysoft.com Received: by 10.159.41.102 with HTTP; Wed, 10 Jan 2018 21:34:13 -0800 (PST) From: Maxim Sobolev Date: Wed, 10 Jan 2018 21:34:13 -0800 X-Google-Sender-Auth: 0pBEklYER5wITT8NAQNlxshcGPY Message-ID: Subject: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2 To: stable@freebsd.org, freebsd-virtualization@freebsd.org Cc: mk@semihalf.com, mw@semihalf.com, FreeBSD Release Engineering Team Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 05:34:15 -0000 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