From owner-freebsd-arm@freebsd.org Mon Oct 19 19:19:51 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 59511432212 for ; Mon, 19 Oct 2020 19:19:51 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-08-4.privateemail.com (mta-08-4.privateemail.com [198.54.122.58]) (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 4CFRQt1CxBz43Cy for ; Mon, 19 Oct 2020 19:19:49 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-08.privateemail.com (localhost [127.0.0.1]) by MTA-08.privateemail.com (Postfix) with ESMTP id C834C6003E for ; Mon, 19 Oct 2020 15:19:42 -0400 (EDT) Received: from mail-il1-f170.google.com (unknown [10.20.151.217]) by MTA-08.privateemail.com (Postfix) with ESMTPA id 8E63860033 for ; Mon, 19 Oct 2020 19:19:42 +0000 (UTC) Received: by mail-il1-f170.google.com with SMTP id p9so1458374ilr.1 for ; Mon, 19 Oct 2020 12:19:42 -0700 (PDT) X-Gm-Message-State: AOAM530dkNq7lgnI2RocIM9sXNFrkthSy8Ng0h7du/OP+OcZk2OQHZ79 NNrqUWQw8WZbmW6JMFUEbEl4htp1lejkY9O0AYM= X-Google-Smtp-Source: ABdhPJyWcANMQZyo6HLocqJF/zOYHZc8s3ZNAJ55U9LrmIw+ZZSnI+x0D1kSANUTqpZVBVxUNo7wOO4Natae8qes7kw= X-Received: by 2002:a92:c843:: with SMTP id b3mr1234559ilq.18.1603135181940; Mon, 19 Oct 2020 12:19:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Vincent Milum Jr Date: Mon, 19 Oct 2020 12:19:28 -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: 4CFRQt1CxBz43Cy X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-arm@darkain.com designates 198.54.122.58 as permitted sender) smtp.mailfrom=freebsd-arm@darkain.com X-Spamd-Result: default: False [-2.73 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:198.54.122.32/27]; NEURAL_HAM_LONG(-1.00)[-1.001]; 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)[198.54.122.58:from]; NEURAL_HAM_SHORT(-0.44)[-0.437]; RCPT_COUNT_TWO(0.00)[2]; 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:198.54.122.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: Mon, 19 Oct 2020 19:19:51 -0000 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 different 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: > > The largest issue currently is that SMP will cause the FreeBSD kernel t= o > panic during boot. > > Could you send the panic? > > I=E2=80=99m guessing lack of spintable support. > > =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 ESXi > installer > and then ESXi itself up and running. > > UEFI builds of FreeBSD ARM64/Aarch64 mostly work "out of the box" under > ESXi > ARM, whereas ARM 32-bit kernels are not supported by any guest OS under > ESXi > ARM. > > There are, however, some areas that could use some improvement, or need > 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 jus= t > 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 format= , > or > convert the raw disk image to ESXi vmdk format. This is how I initially g= ot > FreeBSD up and running prior to the 2020-10-15 snapshot. > > Every version of FreeBSD I've tested on ARM is lacking several drivers by > default. > > uhci for USB 2.0 is not enabled by default. Ensure your VM is initially s= et > 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 virtua= l > mouse, so add this post install if you want mouse support: ums_load=3D"YE= S" > > vmxnet and pvscsi are not pre-compiled. However, they compile and operate > perfectly as expected without any modification on ARM. > > vmci has some x86 assembly that I've not dug into yet, so that is current= ly > not > working. > > I've documented in detail, and continue to update as I test more drivers > over on > my blog: > https://vincerants.com/freebsd-on-esxi-arm-fling-fixing-virtual-hardware/ > > > 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, an= d > 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 FreeBSD > under > ARM. There is currently a patch open with VMware with my changes to the > codebase > to make it functional. To make things easy, I've uploaded some pre-compil= ed > binaries to my blog, as well as included steps to compile this customized > package yourself. The blog will also be updated as development progresses > upstream with VMware. > > https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fli= ng/ > > Xorg desktop runs, and is mostly functional. I've yet to get the > xf86-input-vmmouse or xf86-video-vmware working. Xorg can use sysmouse an= d > 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 drivers > working. > https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5693 > > > I welcome any additional feedback on getting FreeBSD to 100% under ESXi > 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" > > > >