You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub just released a macos-14 runner that is aarch64. I tried it as the host for FreeBSD and OpenBSD arm64 (specifying hypervisor: qemu for both), guessing that it wouldn't work without an update to the Action, and indeed it didn't. Guessing this is reproducible and neither surprising nor interesting, but happy to provide more details if any of those aren't the case.
Would be awesome to be able to run arm64 VMs virtualized, rather than emulated.
The text was updated successfully, but these errors were encountered:
If an aarch64-native macOS qemu doesn't arrive on its own, I guess there's always Homebrew, and if for some reason no qemu cask is available, there's always actions/cache to save off and restore the binaries instead of building every time. Happy to try to help here if needed.
Unfortunately the M1 hardware, which is what the GitHub runners are using, doesn't support hardware accelerated nested virtualization. The Internet says the M2 hardware supports it, but it's unclear if the underly Hypervisor framework supports it for M2.
GitHub just released a
macos-14
runner that is aarch64. I tried it as the host for FreeBSD and OpenBSD arm64 (specifyinghypervisor: qemu
for both), guessing that it wouldn't work without an update to the Action, and indeed it didn't. Guessing this is reproducible and neither surprising nor interesting, but happy to provide more details if any of those aren't the case.Would be awesome to be able to run arm64 VMs virtualized, rather than emulated.
The text was updated successfully, but these errors were encountered: