Running current in Parallels 16.3.2

[Vincent Milum Jr]

We had similar issues getting FreeBSD SMP working under ESXi ARM Fling. In
that instance, there were bugs in both the hypervisor as well as in FreeBSD.

With the FreeBSD kernel fixes, I tested those on Parallels last night, but
still no go with SMP. There is possibly more work to do in the kernel, but
may also be some bugs in the hypervisor as well.

For ESXi ARM Fling, the issues all revolved around the GIC (Generic
Interrupt Controller) and the way inter-CPUs communication happened. If
memory serves me correctly, one CPU core was waiting on another CPU core to
finish initialization and report back in a "ready" state so to speak. Where
Parallels with FreeBSD is hanging, and how it is hanging, looks virtually
identical from my very limited testing last night.

On Wed, Feb 17, 2021 at 3:05 PM Michael Tuexen <tuexen at freebsd.org> wrote:

> Dear all,
>
> I tried running current on an ARM-based Mac using the technical preview of
> Parallels.
> With using only a single CPU, everything seems to run fine. One can git
> clone the
> source tree, do a buildworld / buildkernel and install it and run it.
> Pretty stable,
> not problems.
>
> When using more than one CPU, the kernel doesn't completely boot. It gets
> stuck after
> reporting that the file system is clean. The system also does not respond
> to keyboard
> input anymore.
>
> Any idea what is going wrong or how to figure out if this is a problem
> related to
> FreeBSD or to Parallels?
>
> Best regards
> Michael
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>