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
> I'm concerned that this might lock mac users into a solution with [worse](https://stackoverflow.com/questions/73605175/why-cant-qemu-get-even-close-to-rosetta-2s-performance-when-translating-x86-to) performance, only some people knowing that it's slower than necessary and even fewer people knowing how to fix it.
What if we could launch UTM instead of qemu? It seems to have gained a CLI recently.
As the linux-builder is ephemeral, my preference would be to merge this despite being slow and leaving it as future work to speed it up which could be done without changing the interface.
Another way we could speed this up in the future is building QEMU with Virtualization support and using Rosetta (currently the patchset isn’t mainlined and don’t yet have the correct entitlements necessary to run Rosetta).
As the
linux-builder
is ephemeral, my preference would be to merge this despite being slow and leaving it as future work to speed it up which could be done without changing the interface.Another way we could speed this up in the future is building QEMU with Virtualization support and using Rosetta (currently the patchset isn’t mainlined and don’t yet have the correct entitlements necessary to run Rosetta).
Originally posted by @Enzime in #262021 (comment)
The text was updated successfully, but these errors were encountered: