> Compiling would presumably try to use a lot of cpu in order to finish quickly, but I could also imagine that while arm64 arches may or may not have good support for clocking up and down based on load, it would still require the kernel and the "virtual" environment to agree on a good way to influence what pretend-frequency the cpu should run at, or how to nicely idle in between tasks and interrupts. If they do not agree on that, I'm guessing it would be full speed at all times.
Maybe this has to do with OpenBSD support in QEMU, together with the OpenBSD drivers and/or kernel. My guess. I found this - maybe the beginning of an answer or lines of inquiry: https://ubos.tech/news/openbsd-arm64-gains-apple-hypervisor-support-new-guest-os-capabilities/ Andy Le mar. 12 mai 2026 à 13:09, Janne Johansson <[email protected]> a écrit : > > I set up an arm64 OpenBSD VM using QEMU on macOS M3. > > 1) Building the fish shell port from source was really long (around 2 > hours - as it was also building tools required for the build). > > Try "pkg_add fish" or if you really need to compile it yourself, allow > ports to pkg_add build dependencies by setting the env var to allow > it. > "man ports" -> search for FETCH_PACKAGES > > > 2) And I also notice that just running the VM is really power-hungry. > > Any clue for resolving these problems? > > Compiling would presumably try to use a lot of cpu in order to finish > quickly, but I could also imagine that while arm64 arches may or may > not have good support for clocking up and down based on load, it would > still require the kernel and the "virtual" environment to agree on a > good way to influence what pretend-frequency the cpu should run at, or > how to nicely idle in between tasks and interrupts. If they do not > agree on that, I'm guessing it would be full speed at all times. > > -- > May the most significant bit of your life be positive. >
