-
-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for M1 Silicon - HVF error: HV_UNSUPPORTED #350
Comments
Running into this as well with the newly released |
@colinrtwhite just a doubt -
When you tried to apply that fix, did you do the whole thing with command line tools install for Xcode (though likely they were already installed...) and did you make sure to add the entitlement to the aarch64 emulator vs x86_64. This whole issue seems like an advanced-user hangout, so I'm guessing you did, but just wanted to check - would be curious to see your workflow run log if you could link it |
@mikehardy I believe so, but it's possible I missed something! Here's the script I wrote to run on CI. |
@colinrtwhite that looks perfect. Disappointed it's not working but with a set -e on the top and the script looking the way it does, I think you'd know if the methodology of your test was wrong. Just the test had sad results. Alas. Thanks for sharing, much appreciated. Guess I'll try to pick apart the other semi-related thread where it appears the new public repo runners behind ubuntu-latest have nested-virt enabled if you can jump through the correct hoops to get the runner user /dev/kvm access and install the qemu packages etc... |
- The recent change to `macos-14` means that we can't use x64 emulator (as currently set). Ideally we would just use ARM64 emulators, but that is blocked by ReactiveCircus/android-emulator-runner#350 though. - Instead I've refactored the CI setup: - Moved most things to run `ubuntu-latest`. We can use the new nested-virt KVM support to make the emulator fast there. - We still use `macos-14` but only for iOS builds in a separate job. This is similar to what I do in Tivi. - Add some hierarchy to the jobs, so that `publish` only happens when all of the other jobs pass. - Benchmark tests do not work (by default) on emulators, which is why they've been failing for a while. We can suppress that error and get them to run but there's little benefit, so it's better to just disable them when running on an emulator.
Does anyone have any further insight into this? Not being able to run the Android emulator on macos-14 is going to become more problematic, as the macos-13 image is not getting Xcode updates (15.3 is only available for macos-14). Looking at actions/runner-images#9460, things don't sound promising. Is there any hope of ever getting the emulator running on macos-14? |
Run tests on macos-13 due to ReactiveCircus/android-emulator-runner#350
Copying the comment from @peterlazar1993 , looks like it could be interesting for theoretical future GitHub Actions runners on M3 chips with macOS Sequoia:
|
They're failing with: ``` HVF error: HV_UNSUPPORTED qemu-system-aarch64-headless: failed to initialize HVF: Invalid argument ``` ref. https://github.com/royalapplications/beyondnet/actions/runs/12652684069/job/35255850116#step:9:124 Likely related to ReactiveCircus/android-emulator-runner#350
M1 Silicon is now supported by macOs runners on GitHub.
I tried to used android-emulator-runner on a setup using M1 and it does not seem to fire up the emulator.
The relevant error message seems to be this:
Below is the full output and the gituhub workflow we are using.
Output:
workflow:
The text was updated successfully, but these errors were encountered: