-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Fatal glibc error: CPU does not support x86-64-v2 #287
Comments
Are you sure you got the correct docker image for your CPU? JATOS has amd64 and arm64. |
Hi Kristian, thanks for your response. |
Hm, strange. I'm not a docker expert. It runs on mine, Ubuntu 22.04 with an AMD processor, no VM. I found this GH issue: ansible/awx#11879. There they recommend "play with CPU driver settings" and change the "cpu emulation/driver" from "kvm64" to "host-passthrough". Whatever that means. |
Well thanks, I was thinking about that, I will try it and let you know. |
With the CPU driver setting "host-passthrough" it works, but of course this variant is not ideal because the VM can no longer be safely moved to another host. So it would still be good to know which CPU flags are needed to check which CPU family supports them. |
That's already something. But I understand the problem, you want to be able to move the VM. But I'm honestly lost here. |
Here some links which helped me: https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html And here the required cpu flags to be compatible: CPU supports x86-64-v2: cx16, lahf, popcnt, sse4_1, sse4_2, ssse3 Hope this info is useful for others with the same issue. |
Hi
I get this error "Fatal glibc error: CPU does not support x86-64-v2" inside container with latest version (amd64).
Any ideas how to fix this?
Thanks
The text was updated successfully, but these errors were encountered: