From owner-freebsd-cloud@freebsd.org Thu Aug 29 05:09:03 2019 Return-Path: Delivered-To: freebsd-cloud@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1E488C9BE8 for ; Thu, 29 Aug 2019 05:09:03 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (gerbercreations.com [71.39.140.16]) by mx1.freebsd.org (Postfix) with ESMTP id 46JrHf18xrz4CJD for ; Thu, 29 Aug 2019 05:09:01 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.15.2/8.15.2) with ESMTP id x7T58xaM076885; Wed, 28 Aug 2019 22:08:59 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.15.2/8.15.2/Submit) id x7T58xDm076884; Wed, 28 Aug 2019 22:08:59 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Wed, 28 Aug 2019 22:08:59 -0700 From: Greg Lewis To: Colin Percival Cc: freebsd-cloud@freebsd.org Subject: Re: Problem building aarch64 AMI on 11/amd64 Message-ID: <20190829050859.GA76856@misty.eyesbeyond.com> References: <20190829041448.GA76344@misty.eyesbeyond.com> <0100016cdbae0218-a9e91de2-9896-46af-8282-e8514876ea00-000000@email.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0100016cdbae0218-a9e91de2-9896-46af-8282-e8514876ea00-000000@email.amazonses.com> User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 46JrHf18xrz4CJD X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of glewis@eyesbeyond.com has no SPF policy when checking 71.39.140.16) smtp.mailfrom=glewis@eyesbeyond.com X-Spamd-Result: default: False [-0.03 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.89)[-0.890,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[eyesbeyond.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.11)[0.106,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.23)[-0.231,0]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:71.39.128.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-0.02)[asn: 209(-0.04), country: US(-0.05)] X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2019 05:09:03 -0000 On Thu, Aug 29, 2019 at 04:41:49AM +0000, Colin Percival wrote: > On 2019-08-28 21:14, Greg Lewis wrote: > > I'm attempting to build a FreeBSD 11.3/aarch64 AMI for EC2 based on the > > instructions in > > > > https://lists.freebsd.org/pipermail/freebsd-cloud/2015-April/000015.html > > > > on my FreeBSD 11.3/amd64 box. > > I didn't MFC all of the bits needed for building ARM64 EC2 images to > stable/11, because some ARMy people told me that it was very unlikely > that the arm64 bits in FreeBSD 11 would boot. > > It's possible that this has changed, but given the level of doubt I > heard from them I suspect you're better off looking for someone who can > give you access to real hardware. Thanks Colin! I will stop banging my head against the wall then :) There is a ref11 box listed on the wiki, but I can't seem to connect, so I'll ping cluster admin and see if I can find out what is up with it. -- Greg