-
Notifications
You must be signed in to change notification settings - Fork 70
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
QEMU 6.2 released with support for Apple M1 Sillicon - Support for AArch64 #175
Comments
And what was your experience running CP with this emulation? |
I cannot say I took scientific measures of that, but my perception is that it improved considerably. Let me share the full context so it makes more sense. Please, bear with me. Elasticsearch does provide an arm64 image so no worries there. As far as I could see, after I updated docker configuration to use qemu 6.2 schema-registry has not crashed until now but I face other problems such as communications with the other aforementioned tools. (EDIT: I started using |
Thanks for the feedback - Given that effort to resolve #117 will be for Confluent to provide natively built docker images (not emulated like we're doing here), I don't think there's anything actionable for confluent to take on this particular issue, and is only here to provide community solutions and work around to #117. |
Please, could you share what is needed to be done so maybe someone in the open source community may try to tackle it ? |
The action lies on Confluent's side of things - as in theres nothing for the community to help with. We need to update our build infrastructure to support building ARM64 docker images. |
Recent changes to QEMU were released and it now supports hvf accelerator for running AArch64 guests.
This might solve the problem reported at #117.
Source:
QEMU 6.2 Changelog
The way I tested it was by installing QEMU 6.2 through homebrew and changing qemu-system-aarch64 (at
/System/Volumes/Data/Users/$USER/Library/Containers/com.docker.docker/Data/tasks/qemu-system-aarch64
) configuration to point to the new version.Please, could you help verifying if the new release of QEMU can help at #117
Thanks for your attention
The text was updated successfully, but these errors were encountered: