From owner-freebsd-arm@freebsd.org  Tue Oct 20 18:40:48 2020
Return-Path: <owner-freebsd-arm@freebsd.org>
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 545A343858B
 for <freebsd-arm@mailman.nyi.freebsd.org>;
 Tue, 20 Oct 2020 18:40:48 +0000 (UTC)
 (envelope-from crowston@protonmail.com)
Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "protonmail.com",
 Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4CG2WM0SQdz4cmF
 for <freebsd-arm@freebsd.org>; Tue, 20 Oct 2020 18:40:46 +0000 (UTC)
 (envelope-from crowston@protonmail.com)
Date: Tue, 20 Oct 2020 18:40:29 +0000
To: Vincent Milum Jr <freebsd-arm@darkain.com>
From: Robert Crowston <crowston@protonmail.com>
Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Reply-To: Robert Crowston <crowston@protonmail.com>
Subject: Re: FreeBSD under VMware ESXi ARM Fling
Message-ID: <KhcHxcOB6jmtZ7YCIkdHDx9-W2Wgu5TeC5hHjTfJsHVIDw20HwR9bVUZ7oyFHAj7SwCQzbI1LMaKKt0YplQy1WCIo4fmaTGpv_MDlYS1Zus=@protonmail.com>
In-Reply-To: <CAOWUMWEXiiw-avXQd9GKKn=xLdgxVKuU=opZ67UfkwnQvJb0GQ@mail.gmail.com>
References: <CAOWUMWF-+Rg2syHnPZN28i1TB0-jr3P_eNsnSTL_48pZGqWjSw@mail.gmail.com>
 <gkECxHG3AZsNQOlRwjvFTnG3WZNYizcF5LicaGDvV1_qzBWqtJW4kSNRSZ-GEI3J8GKEjifr7kq-xBnGb-SjjjQt33MgoLsSTTQUubYVyh8=@protonmail.com>
 <CAOWUMWGWECs2VVo9afE5KB5csAQGCEq-=d4EbSJP5kFxv2mg5w@mail.gmail.com>
 <MZwl7SSjlHcZjH-qrI8Y2N96hag_TxajCc0K-Lmk6dPB7G64Nn7xm2e9ciPi8t9lK7yzgonrcy2zchruftUdat-FzCTbiUKJ8xu0Zr8fED0=@protonmail.com>
 <CAOWUMWEXiiw-avXQd9GKKn=xLdgxVKuU=opZ67UfkwnQvJb0GQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no
 autolearn=disabled version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 mailout.protonmail.ch
X-Rspamd-Queue-Id: 4CG2WM0SQdz4cmF
X-Spamd-Bar: ---
X-Spamd-Result: default: False [-3.95 / 15.00];
 HAS_REPLYTO(0.00)[crowston@protonmail.com];
 TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[];
 FREEMAIL_FROM(0.00)[protonmail.com];
 R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24];
 DKIM_TRACE(0.00)[protonmail.com:+]; RCPT_COUNT_TWO(0.00)[2];
 DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine];
 NEURAL_HAM_SHORT(-0.96)[-0.955]; RCVD_COUNT_ZERO(0.00)[0];
 FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+];
 FREEMAIL_ENVFROM(0.00)[protonmail.com];
 ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH];
 MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[];
 NEURAL_HAM_MEDIUM(-0.99)[-0.987];
 R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail];
 REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[];
 NEURAL_HAM_LONG(-1.01)[-1.012]; MIME_GOOD(-0.10)[text/plain];
 FREEMAIL_REPLYTO(0.00)[protonmail.com];
 TO_MATCH_ENVRCPT_SOME(0.00)[];
 RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.18:from];
 MAILMAN_DEST(0.00)[freebsd-arm]
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.33
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 18:40:48 -0000

> According to the ESXi devs, there is no SIO controller currently, and I b=
elieve 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 yo=
u add boot_verbose=3D"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.