-
Notifications
You must be signed in to change notification settings - Fork 820
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
Illegal instruction (core dumped) on Ubuntu 20.04, AVX2 #487
Comments
No luck, unfortunately. Tried it with the VM I was using as well as a new one (same OS) |
Just to confirm, if you |
It does not -- will figure out what's going wrong on my end. |
If you can't get AVX enabled on the VM you can always build MuJoCo from source with AVX disabled. |
I've followed the StackOverflow solution (as well as the potential solution described in the problem) and despite successfully disabling Hyper-V I have not been able to get my VM access to AVX/AVX2. Any advice? |
At this point I think you should just build everything (MuJoCo and Python bindings) from source. |
Hi @xRiis, were you able to solve things via Saran’s suggestion? |
I tried the something twice, and I met the same issue. I didn't find how to build MuJoCo from source with AVX disabled. May I have a link to the steps? I appreciate that. |
Sorry for the late response. When using CMake, you should be able to specify |
Did anyone manage to recompile Mujoco and the python bindings from source with AVX disabled? I'm having the same problem trying to run Ubuntu in Virtualbox. |
Hi all, it looks like Mujoco is unusable on my machine. Error is in the title: Illegal instruction (core dumped)
OS: Ubuntu 20.04.5 (running through VirtualBox)
CPU: i9-12900K
Using Mujoco 2.2.1
This occurs as soon as I try to import Mujoco in a Jupyter notebook. I cannot manage to get Mujoco working on the latest Win11 release, either. I have tried installing Mujoco both by pip and from source, in case there was some issue with the package not properly recognizing my CPU architecture.
Our hypothesis is that there's some issue caused by my processor's asm being AVX2 rather than AVX.
The text was updated successfully, but these errors were encountered: