Date: Mon, 22 Feb 2021 22:42:25 +0100 From: tuexen@freebsd.org To: Vincent Milum Jr <freebsd-arm@darkain.com> Cc: freebsd-arm@freebsd.org Subject: Re: Running current in Parallels 16.3.2 Message-ID: <08F81EB7-251B-4CCC-911E-4094A83FE356@freebsd.org> In-Reply-To: <CAOWUMWH-7fjBdf%2BEnKospFTU2Y7LmmOa0NrJFo1Uc_9kjNMaMQ@mail.gmail.com> References: <5189D185-4A1F-43A0-A61D-E3D24CC74B3D@freebsd.org> <CAOWUMWH-7fjBdf%2BEnKospFTU2Y7LmmOa0NrJFo1Uc_9kjNMaMQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> On 18. Feb 2021, at 00:28, Vincent Milum Jr <freebsd-arm@darkain.com> wrote: > > 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. If you boot into single user mode, the system comes up and uses multiple CPUs. Then using ^D to start multi user mode shows that mount seems to hang. You can use ^T, but it never finishes. Is that what you observed on ESXi? Best regards Michael > > On Wed, Feb 17, 2021 at 3:05 PM Michael Tuexen <tuexen@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@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> > _______________________________________________ > 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"home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?08F81EB7-251B-4CCC-911E-4094A83FE356>