From owner-freebsd-arm@freebsd.org Mon Oct 19 20:52:24 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 2604A434A1B for ; Mon, 19 Oct 2020 20:52:24 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch [185.70.40.134]) (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 4CFTTf2gmLz4Bst for ; Mon, 19 Oct 2020 20:52:21 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Mon, 19 Oct 2020 20:52:10 +0000 To: Vincent Milum Jr From: Robert Crowston Cc: "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: FreeBSD under VMware ESXi ARM Fling Message-ID: In-Reply-To: References: 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: 4CFTTf2gmLz4Bst X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.58 / 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.58)[-0.577]; 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.985]; 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.134: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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2020 20:52:24 -0000 My initial hypothesis was wrong. I had meant, can you provide a text copy of the dmesg (collected from a ser= ial port!)! But, from the video, it seems that as soon as we get to the Release APs pha= se, there is some race condition that is causing text to be concurrently wr= itten to the screen by multiple processors--you can see it becomes garbled.= KDB is entered shortly before the "Release APs..." is printed to the scree= n, but text continues to be written to the console. [We don't really know i= n what order these events happen, though.] A panic() is triggered within a = few moments. At this point, we enter termcn_cnputc(), and violate a KASSERT= in __mtx_lock_spin_flags. This causes a recursive panic. For me the next logical step would be to attach a debugger to the guest pro= cess. Any idea if ESXi ARM allows debug or single stepping of guests? -- RHC. On Mon, Oct 19, 2020 at 20:19, Vincent Milum Jr w= rote: > I'm not too familiar with the FreeBSD kernel itself. Here is a recording = of booting the VM from the 13.0 2020-10-15 Snapshot ISO. There are a few di= fferent outcomes that seem to randomly happen when booting. > > https://www.youtube.com/watch?v=3DLs9gkQ14Z-A > > On Mon, Oct 19, 2020 at 11:49 AM Robert Crowston wrote: > > > >=C2=A0The largest issue currently is that SMP will cause the FreeBSD k= ernel to > > panic=C2=A0during boot. > > > > Could you send the panic? > > > > I=E2=80=99m guessing lack of spintable support. > > > > =C2=A0 =C2=A0 =E2=80=94 RHC. > > > > On Mon, Oct 19, 2020 at 07:19, Vincent Milum Jr wrote: > > > > > Recently, VMware released what they're calling "ESXi ARM Fling" - an > > > ARM64/Aarch64 version of VMware ESXi server. > > > > > > Details of the release along with the download can be found here: > > > https://flings.vmware.com/esxi-arm-edition > > > > > > They support a number of ARM platforms already, most notably is the > > > Raspberry Pi > > > 4 (only 4GB and 8GB models). They have instructions on their site on = how to > > > install and configure the UEFI firmware on the Pi for getting the ESX= i > > > installer > > > and then ESXi itself up and running. > > > > > > UEFI builds of FreeBSD ARM64/Aarch64 mostly work "out of the box" und= er ESXi > > > ARM, whereas ARM 32-bit kernels are not supported by any guest OS und= er ESXi > > > ARM. > > > > > > There are, however, some areas that could use some improvement, or ne= ed some > > > massive work to get working. > > > > > > The largest issue currently is that SMP will cause the FreeBSD kernel= to > > > panic > > > during boot. A VM with only one single vCPU however will boot and run= just > > > fine. > > > > > > Prior to the 13.0-CURRENT snapshot 2020-10-15, the CD-Rom driver was = not > > > included with the ARM64 builds, so the ISO would fail to mount itself= on > > > boot. This > > > means the easiest way to try earlier versions, such as 12.1-RELEASE, = you'll > > > need > > > to either convert the pre-built vmdk file from Workstation to ESXi fo= rmat, > > > or > > > convert the raw disk image to ESXi vmdk format. This is how I initial= ly got > > > FreeBSD up and running prior to the 2020-10-15 snapshot. > > > > > > Every version of FreeBSD I've tested on ARM is lacking several driver= s by > > > default. > > > > > > uhci for USB 2.0 is not enabled by default. Ensure your VM is initial= ly set > > > up > > > for USB 3.1 so the virtual keyboard and mouse will function. This is = easy > > > enough > > > to fix post install with: uhci_load=3D"YES" > > > > > > ums is the same as above. ESXi ARM uses USB instead of PS2 for the vi= rtual > > > mouse, so add this post install if you want mouse support: ums_load= =3D"YES" > > > > > > vmxnet and pvscsi are not pre-compiled. However, they compile and ope= rate > > > perfectly as expected without any modification on ARM. > > > > > > vmci has some x86 assembly that I've not dug into yet, so that is cur= rently > > > not > > > working. > > > > > > I've documented in detail, and continue to update as I test more driv= ers > > > over on > > > my blog: > > > https://vincerants.com/freebsd-on-esxi-arm-fling-fixing-virtual-hardw= are/ > > > > > > The ESXi UI has a known bug in that it'll list some virtual hardware = that > > > doesn't actually exist inside of the VM. These are all legacy devices= , and > > > should be easy enough to figure out. There are no virtual IDE/ATA or = PS2 > > > ports. > > > Keyboard and mouse now use the virtual USB controller instead. > > > > > > open-vm-tools has required a bit of work to make functional on FreeBS= D under > > > ARM. There is currently a patch open with VMware with my changes to t= he > > > codebase > > > to make it functional. To make things easy, I've uploaded some pre-co= mpiled > > > binaries to my blog, as well as included steps to compile this custom= ized > > > package yourself. The blog will also be updated as development progre= sses > > > upstream with VMware. > > > https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm= -fling/ > > > > > > Xorg desktop runs, and is mostly functional. I've yet to get the > > > xf86-input-vmmouse or xf86-video-vmware working. Xorg can use sysmous= e and > > > the > > > console framebuffer for rendering, and this is working okay for basic > > > testing > > > right now. > > > > > > I also have an early dmesg, but this was from before getting most dri= vers > > > working. > > > https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5693 > > > > > > I welcome any additional feedback on getting FreeBSD to 100% under ES= Xi ARM! > > > > > > - Vince (darkain) > > > _______________________________________________ > > > freebsd-arm@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org= "