-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
Unable to run on Windows ARM with Snapdragon X Elite #534
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
i got wsl logs via collect-wsl-logs and i am analyze it right now |
Just to be sure: Did you build your own tarball targeting aarch64-linux? The one from our releases is for x86_64 and will not run on ARM |
@nzbr cool, but how?, i have nix on my other x86 machine, so how i can force it to build for aarch64? |
hello i build via debian arm wsl, with this commit #530 and it still did not work, the error it appear to cause the problem is
|
also there was an error that it did not found swap.vhdx so i copied debian swap.vhdx to it path , and it got fixed |
If you are using a flake based config it should be something like outputs = { self } @inputs:
nixosConfigurations.<hostname> = {
/* ... */
system = "aarch64-linux";
}; Or are you talking about cross compiling? |
@RoadRoller01 where did you get those logs from? What does |
i got the logs from wsl, via https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1 |
dmesg? do you mean the |
The VM is shared, so |
oooh okay 👍, i can’t do it right now, so i will send it tomorrow. |
I tried using this |
WslLogs-2024-10-17_13-20-21.zip |
Bug description
NixOS imports fine on Windows ARM but when attempting to run NixOS via
wsl -d NixOS
the following error is thrown on Windows ARM with a Snapdragon X Elite (Microsoft Surface 7):Happy to get more detailed logs if needed (not sure how though). Not sure if it's relevant but Ubuntu and Kali Linux both seem to work fine.
To Reproduce
wsl -d NixOS
Logs
WSL version
The text was updated successfully, but these errors were encountered: