Skip to content
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

Disable Rosetta for VZ VM #554

Closed
Sangeppato opened this issue Jan 2, 2023 · 4 comments · Fixed by #555
Closed

Disable Rosetta for VZ VM #554

Sangeppato opened this issue Jan 2, 2023 · 4 comments · Fixed by #555
Labels
enhancement New feature or request

Comments

@Sangeppato
Copy link

Description

First of all, thank you for your amazing work.

It looks like Lima has some performance issue when using VZ and Rosetta.
From my understanding, Rosetta is automatically enabled in Colima when VZ is used, with no way to manually disable it (the Lima overrides don't work).
Would you consider adding such an option?

@abiosoft abiosoft added the enhancement New feature or request label Jan 2, 2023
@abiosoft
Copy link
Owner

abiosoft commented Jan 2, 2023

Yeah, definitely. We have no idea Rosetta has a negative effect.

@rfay
Copy link
Contributor

rfay commented Jan 2, 2023

I would actually be in favor of rosetta being disabled by default. It has potential for enormous confusion, because wrong-arch binaries inside container might work or might not... It's amazing that it might be able to add value, but allowing it by default seems like a prescription for lots of impossible support requests.

@chadlwilson
Copy link

FWIW, there might be an example (in part?) of such confusion at swiftlang/swift#62725 - note at the bottom sporadic rosetta errors (Virtualization.Framework / aarch64 / virtiofs). Unclear if the root cause was some Rosetta problem or Virtualization.Framework or virtiofs - lots of different variables :-)

@mapkon
Copy link

mapkon commented Jan 3, 2023

Yeah, probably related. I moved the ticket here #539 -

The issue disappeared when we switched to QEMU as opposed to MacOS.Virtualization.Framework. I am wondering if that is something that should be avoided at all costs.

@abiosoft Let me know if you need more information on that issue, or it will be addressed in this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants