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

Fatal glibc error: CPU does not support x86-64-v2 #287

Open
webadmin-psychologie opened this issue Apr 26, 2023 · 7 comments
Open

Fatal glibc error: CPU does not support x86-64-v2 #287

webadmin-psychologie opened this issue Apr 26, 2023 · 7 comments

Comments

@webadmin-psychologie
Copy link

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

@kristian-lange
Copy link
Member

Are you sure you got the correct docker image for your CPU? JATOS has amd64 and arm64.
Best,
Kristian

@webadmin-psychologie
Copy link
Author

Hi Kristian, thanks for your response.
Yes, pretty sure, when I inspect the downloaded "jatos/jatos:latest" image, I see "Architecture": "amd64". Perhaps important to know, Docker runs inside a VM with the default CPU settings "kvm64", do I need to select a specific CPU type or enable certain CPU flags?
Best, Pete

@kristian-lange
Copy link
Member

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.

@webadmin-psychologie
Copy link
Author

Well thanks, I was thinking about that, I will try it and let you know.

@webadmin-psychologie
Copy link
Author

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.

@kristian-lange
Copy link
Member

That's already something. But I understand the problem, you want to be able to move the VM. But I'm honestly lost here.

@webadmin-psychologie
Copy link
Author

Here some links which helped me:

https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/x86/include/asm/cpufeatures.h

And here the required cpu flags to be compatible:

CPU supports x86-64-v2: cx16, lahf, popcnt, sse4_1, sse4_2, ssse3
CPU supports x86-64-v3: avx, avx2, bmi1, bmi2, f16c, fma, abm, movbe, xsave
CPU supports x86-64-v4: avx512f, avx512bw, avx512cd, avx512dq, avx512vl

Hope this info is useful for others with the same issue.

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

No branches or pull requests

2 participants