-
Notifications
You must be signed in to change notification settings - Fork 103
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 Apple Silicon virtualized processor #229
Comments
@pthariensflame is your host Mac running a M3 variant? Since in my testings (M1/M2 only so far) the Virtualization framework set the relevant MIDR_EL1 bits all to 0 but in your output the vendor info ( |
It is indeed; it's an M3 Max. Here is
|
I don't think there is much to do here. Identifying the underlying M3 is not possible due to MIDR being all zeros except for the implementer, which does not give enough information. It could be indeed reported as running under a VM called "UTM" or whatever, but cpufetch only supports virtualization detection under x86, not ARM, mainly because I don't know a proper way to detect virtualization. If you know of any please let me know, otherwise I think it's better to close this for now. |
Running in a Fedora VM under macOS (via UTM in Virtualization.framework mode) results in the following output:
cpufetch --verbose
:cpufetch --debug
:This could probably be described as "Apple Silicon Virtual CPU" or similar.
The text was updated successfully, but these errors were encountered: