Hi, Is there any plans to support the Raspberry Pi 5 on release?

Hi! In order to run ESXi Arm fling on the Raspberry Pi 5, there are some requirements from the firmware side.

If the Raspberry Pi 5 meets the Arm SystemReady ES requirements on launch (see https://www.arm.com/architecture/system-architectures/systemready-certification-program/es) there are high chances the ESXi Arm fling will run on it on release.

Running the new September 1st ESXi image. While managed by a vcenter 7.0.3 host I'm seeing the Arm hosts failing a bunch of skyline health security checks for CVEs dating all the way back to 2020. Is this a known compatibility issue with skyline health or is it worth filing a bug against this with the fling team?

Hi Eugene, thanks for the question! The fling is based on ESXi 7.0 version, and is not supported for security issues, CVEs. It is not production ready, and should not be used for production.

Thus the skyline health reports are expected, and won't be fixed for the fling v1.x.

Thanks,
Cyprien

Dear ESXi-on-Arm team,

If Core don't support SDEI,It will not affect entering the OS?

Hi Zouf, the ESXi Arm Fling does not support SDEI.

Thanks for answer my question.

One more question,the ESXi Arm Fing' GRUB display call is not UEFI gST->ConOut?

I suppose you are talking about the ESXi boot itself (and it's not using GRUB). The ESXi bootloader is using its own GOP driver and/or serial port directly, and not ConOut.

Thank you.

I used Phytium2000 and Phytium2500 Core.And Phytium2500 Can display bootloader,but Phytium2000 Can't display.

Is there anything I can do for it?

I don't know why it "can't", but you can try manually starting bootaa64.efi from the UEFI shell, adding the -S1 option to enable serial port usage (1 as COM1).

Any plans for proper networking support on LX2160 platforms?

Hi, unfortunately we can't announce anything. For sure I'd like to have it working (having 2 Honeycomb platforms myself...)!