From owner-freebsd-arm@freebsd.org Tue Oct 20 18:48:02 2020 Return-Path: Delivered-To: freebsd-arm@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 898B44381F0 for ; Tue, 20 Oct 2020 18:48:02 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-07-4.privateemail.com (mta-07-4.privateemail.com [68.65.122.27]) (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 4CG2gj5BgLz4dCV for ; Tue, 20 Oct 2020 18:48:01 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-07.privateemail.com (localhost [127.0.0.1]) by MTA-07.privateemail.com (Postfix) with ESMTP id E905F6004E for ; Tue, 20 Oct 2020 14:47:59 -0400 (EDT) Received: from mail-il1-f169.google.com (unknown [10.20.151.238]) by MTA-07.privateemail.com (Postfix) with ESMTPA id BC8CF60047 for ; Tue, 20 Oct 2020 18:47:59 +0000 (UTC) Received: by mail-il1-f169.google.com with SMTP id n5so3669282ile.7 for ; Tue, 20 Oct 2020 11:47:59 -0700 (PDT) X-Gm-Message-State: AOAM533XGMsADy8ucmNPgffF0qrOgRtqvtiZ6PVX/bso5IVb36PxjkQr kDd20L95OvcX/ZBobTHuC7votSqMDqapzP9CxYA= X-Google-Smtp-Source: ABdhPJxX3h0942kWBzPHgdtGmxxwpqa7EfOwfTjQHRfyfisSBW5uh0sAjb+RvvO5OT00MglCSWayeHzJwj1m+WbE1k0= X-Received: by 2002:a05:6e02:541:: with SMTP id i1mr2849826ils.156.1603219679085; Tue, 20 Oct 2020 11:47:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Vincent Milum Jr Date: Tue, 20 Oct 2020 11:47:45 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD under VMware ESXi ARM Fling To: Robert Crowston Cc: "freebsd-arm@freebsd.org" X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 4CG2gj5BgLz4dCV X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-arm@darkain.com designates 68.65.122.27 as permitted sender) smtp.mailfrom=freebsd-arm@darkain.com X-Spamd-Result: default: False [-2.95 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:68.65.122.0/27]; NEURAL_HAM_LONG(-1.01)[-1.007]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[darkain.com]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[68.65.122.27:from]; NEURAL_HAM_SHORT(-0.64)[-0.638]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.65.122.27:from]; NEURAL_HAM_MEDIUM(-1.01)[-1.009]; FREEMAIL_TO(0.00)[protonmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:22612, ipnet:68.65.122.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2020 18:48:02 -0000 Most of those instructions are just for "update the RPi's firmware" - if you're on a new enough firmware already, you can skip that entire section involving Raspberry Pi OS. After that, they just provide an installer image which can be used to install to either local storage, or remote network storage. It is being treated more like a typical x86 workflow rather than what we're more familiar with for ARM/SBC workflows. On Tue, Oct 20, 2020 at 11:40 AM Robert Crowston wrote: > > According to the ESXi devs, there is no SIO controller currently, and I > believe this is required for the virtual serial ports to work > > https://flings.vmware.com/esxi-arm-edition/bugs/1104 > > I do think this a requirement. Indeed, a UART is detected in your dmesg: > > uart0: <16550 or compatible> mem 0x3fff03f8-0x3fff03ff irq 5 on ofwbus0 > uart0: console (230400,n,8,1) > > Is it not exposed on the host? > > If we cannot debug, a verbose boot would at least add some colour. Could > you add boot_verbose="YES" to /etc/loader.conf? > > I took a look at the instructions for getting this up and running on my > own Pi. It is certainly a lot of instructions. It is a shame they do not > just provide a .img I could flash to an sdcard. > > -- RHC. > > >