general/other Virtualizing FreeBSD 14 CURRENT on macOS M2 via Parallels 19

[jhgorse]

Greetings,

I am having an issue with post install and the install disc1 iso of FreeBSD 14 CURRENT arm64 on macOS M2 via Parallels 19. It seems to have installed, but after a few moments of running, either the 14 installer or the installed OS, I receive console spam of this error message:

AcpiOsExecute: failed to enqueue task, consider increasing debug.acpi.max_tasks tunable

Which seems to be addressable by changing debug.acpi.max_tasks="128" in
/boot/loader.conf.
* https://forums.freebsd.org/threads/...tery-not-properly-detected.29164/#post-162939

However, I cannot seem to last long enough to make this modification before the spam occurs. FBSD 13 works fine on macOS Parallels 19 so I tried the modification with that rescue cd. It cannot mount with the new ZFS feature flag, com.klarasystems:vdev_zaps_v2 . FBSD 14 uses ZFS 2.2+ and FBSD 13 uses 2.1+, requiring an update to the EFI System Partition (ESP) to mount properly for boot.

How do you suppose I might make that modification or squelch the spammed message in FBSD 14?

Cheers,
Joe

Additional References
* https://forum.parallels.com/threads...s-it-does-work-on-apple-silicon.355398/page-2
* https://www.reddit.com/r/freebsd/comments/17lr56p/apple_m2_support/

 

[SirDice]

FreeBSD 14 CURRENT arm64

This is old and doesn't exist anymore.

Topics about unsupported FreeBSD versions

The FreeBSD Forums cater primarily to end-users and systems administrators. As such, the Forums focus almost exclusively on FreeBSD versions that are officially supported according to the official FreeBSD website. Since resources are scarce, the FreeBSD Forums strongly suggest that anyone asking...

forums.freebsd.org

 

[T-Daemon]

install disc1 iso of FreeBSD 14 CURRENT arm64

Currently supported versions are 13.3-RELEASE(-STABLE), 14.0-RELEASE(-STABLE), 14.1-PRERELEASE. Not counting 13.2-RELEASE here, it will be end-of-life in June 2024.

a -CURRENT snapshot is not recommended for end users, unless you want do development or testing.

but after a few moments of running, either the 14 installer or the installed OS, I receive console spam of this error message:

However, I cannot seem to last long enough to make this modification before the spam occurs.

Those messages are displayed on the first (system) console, the one you see the boot and error messages displayed. FreeBSD has in the default terminal configuration besides the first console 7 virtual consoles (terminals). See /etc/ttys and ttys(5).

To edit /boot/loader.conf without being disturbed by console messages change into a virtual console with key combination Alt+[F2 - F8].

See FreeBSD handbook, chapter 3.2.1. Virtual Consoles

 

[jhgorse]

Ah, you got me. The old `snapshots` vs `releases` tree:

Index of /releases/ISO-IMAGES/

Index of /snapshots/ISO-IMAGES/

Yes, I understand CURRENT is generally unsupported except in dev channels. I was hoping to triage here before spamming the mailing list with my novice issues.

Thank you T-Daemon for the references!

Even though it's old, I've posted the work for others to enjoy with vagrant on arm64 parallels:

Vagrant Cloud by HashiCorp

Vagrant Cloud by HashiCorp

app.vagrantup.com

I may do 14.1 and 15 PRERELEASE for fun later. It might be interesting to set up a `packer` CI/CD flow for it.

 

[karbhawono]

Greetings,

I am having an issue with post install and the install disc1 iso of FreeBSD 14 CURRENT arm64 on macOS M2 via Parallels 19. It seems to have installed, but after a few moments of running, either the 14 installer or the installed OS, I receive console spam of this error message:

AcpiOsExecute: failed to enqueue task, consider increasing debug.acpi.max_tasks tunable

Which seems to be addressable by changing debug.acpi.max_tasks="128" in
/boot/loader.conf.
* https://forums.freebsd.org/threads/...tery-not-properly-detected.29164/#post-162939

However, I cannot seem to last long enough to make this modification before the spam occurs. FBSD 13 works fine on macOS Parallels 19 so I tried the modification with that rescue cd. It cannot mount with the new ZFS feature flag, com.klarasystems:vdev_zaps_v2 . FBSD 14 uses ZFS 2.2+ and FBSD 13 uses 2.1+, requiring an update to the EFI System Partition (ESP) to mount properly for boot.

How do you suppose I might make that modification or squelch the spammed message in FBSD 14?

Cheers,
Joe

Additional References
* https://forum.parallels.com/threads...s-it-does-work-on-apple-silicon.355398/page-2
* https://www.reddit.com/r/freebsd/comments/17lr56p/apple_m2_support/

Hi Joe jhgorse ,

I'm having this same issue

AcpiOsExecute: failed to enqueue task, consider increasing debug.acpi.max_tasks tunable

using FreeBSD 14-RELEASE and wondering if you have found any solution or workaround ?

Regards,

-ak-

 

[SirDice]

using FreeBSD 14-RELEASE

I'm assuming that's 14.0. Have you tried BETA2 of 14.1 yet?

 

[karbhawono]

I'm assuming that's 14.0. Have you tried BETA2 of 14.1 yet?

Yes SirDice , I did try 14.1 BETA 2. The issue is still there.

 

[SirDice]

Did you also try setting debug.acpi.max_tasks="128" in /boot/loader.conf?

 

[karbhawono]

Did you also try setting debug.acpi.max_tasks="128" in /boot/loader.conf?

Yes, I tried 128 and higher.

 

[SirDice]

Then I'm out of ideas or suggestions. I think we do have a couple of users with an M1/M2 Mac. So stick around, maybe one of them might have some ideas.

 

[karbhawono]

Then I'm out of ideas or suggestions. I think we do have a couple of users with an M1/M2 Mac. So stick around, maybe one of them might have some ideas.

Will do and thanks for the suggestions.

 

[T-Daemon]

karbhawono and jhgorse, try 15-CURRENT.

The issue has been fixed since 2023-10-12 on the "main" development branch (15-CURRENT) after Differential Revision: https://reviews.freebsd.org/D42158.

Note this fixes a bug where an arm64 server [...] at boot, with:
"AcpiOsExecute: failed to enqueue task, consider
increasing the debug.acpi.max_tasks tunable" scrolling
on console.

But the patch hasn't landed on latest release, release/14.1 (14.1-BETA2), or stable/14.

The patch provides a tunable (debug.acpi.ged_defer). For details see commit log message of the patch down below.

. https://cgit.freebsd.org/src/commit/?id=be91b4797e2c8f3440f6fe3aac7e246886f9ebca

If the tunable has an effect, you can try patching 14.0-RELEASE or 14.1-BETA2 source, eventually stable/14 .

 

[karbhawono]

karbhawono and jhgorse, try 15-CURRENT.

The issue has been fixed since 2023-10-12 on the "main" development branch (15-CURRENT) after Differential Revision: https://reviews.freebsd.org/D42158.


But the patch hasn't landed on latest release, release/14.1 (14.1-BETA2), or stable/14.

The patch provides a tunable (debug.acpi.ged_defer). For details see commit log message of the patch down below.

. https://cgit.freebsd.org/src/commit/?id=be91b4797e2c8f3440f6fe3aac7e246886f9ebca

If the tunable has an effect, you can try patching 14.0-RELEASE or 14.1-BETA2 source, eventually stable/14 .

Hi T-Daemon , I'm using FreeBSD-15.0-CURRENT-arm64-aarch64-20240509-ce7756fdca1f-270021-disc1.iso and it was successfully installed.

However, it panic on first boot.


-ak-

 

[karbhawono]

Hi T-Daemon , I'm using FreeBSD-15.0-CURRENT-arm64-aarch64-20240509-ce7756fdca1f-270021-disc1.iso and it was successfully installed.

However, it panic on first boot.

View attachment 19073
-ak-

I managed to boot after commenting out ipv6 in /etc/rc.conf but unexpected kernel panic still happening.

 

[cracauer@]

I had no problems running 15-current in Parallels on my M1. But I can't re-check since I don't have a spare license for my M1 Mac.

 

[T-Daemon]

I managed to boot after commenting out ipv6 in /etc/rc.conf but unexpected kernel panic still happening.

Such issues are not unexpected on a development branch. Please set the tunable debug.acpi.ged_defer=1 in /boot/loader.conf and check if the error messages have disappeared.