Wikipedia lists for x86-64-v2:
Intel Nehalem and newer Intel “big” cores
Intel (Atom) Silvermont and newer Intel “small” cores
AMD Bulldozer and newer AMD “big” cores
AMD Jaguar
VIA Nano and Eden “C”
I’d say: pick “latest and greatest” that all your baremetal servers support. (One is not likely … Answer from jlehtone on forums.rockylinux.org
GitHub
github.com › keycloak › keycloak › issues › 17290
Fatal glibc error: CPU does not support x86-64-v2 · Issue #17290 · keycloak/keycloak
February 26, 2023 - I'm trying to build my docker container based on keycloak:21.0, but it fails on build.sh, and says: Fatal glibc error: CPU does not support x86-64-v2
Author keycloak
Rocky Linux Forum
forums.rockylinux.org › rocky linux help & support
Fatal glibc error: CPU does not support x86-64-v2 - Rocky Linux Help & Support - Rocky Linux Forum
May 29, 2024 - I have received this error on VCenter 7, how can I fix it? Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Hi! A Mysql container is throwing this error and doesn’t start: Fatal glibc error: CPU does not support x86-64-v2 It’s running on a Debian 11 server and used together with Piwigo. The cpu seems to support sse2: gustavo@srv2:~/docker/piwigo$ sudo grep -o sse2 /proc/cpuinfo sse2 sse2 The ... More on discourse.linuxserver.io
0
0
May 11, 2024Fatal glibc error: CPU does not support x86-64-v2
Wazuh version Install type Action performed Platform 4.8.0 Manager Install / Upgrade Proxmox ≤ 7.x Description Users have reported encountering the following error while running our packages: Fatal glibc error: CPU does not support x86-6... More on github.com
5
June 19, 2024Fatal glibc error: CPU does not support x86-64-v2
You're using VirtualBox, and for one reason or another, it is presenting a virtual CPU with reduced functionality to the guest. CentOS Stream 9 and related releases will not run on CPUs (physical or virtual) with reduced functionality. The problem is not your hardware, it's the configuration of VirtualBox. Unfortunately, all of the discussions I can find about enabling modern features are > 10 years old, and I can't find anything in VirtualBox's official documentation. I'm sure a configuration option is there... somewhere. This document suggests the CPU extensions should be enabled by default: https://www.virtualbox.org/manual/ch09.html#sse412passthrough I'd look around more, in that direction More on reddit.com
3
2
July 15, 2024After upgrade, PMM2 container fails to start with "Fatal glibc error: CPU does not support x86-64-v2"
Only error msg from “docker logs …” is Fatal glibc error: CPU does not support x86-64-v2 I see there’s a (new?) requirement “Your CPU must support the SSE4.2 instruction set… If your CPU is lacking this instruction set you won’t be able to use Query Analytics.” In /proc/cpuinfo ... More on forums.percona.com
5
0
July 31, 2023Why do new Linux versions fail on old CPUs?
They use faster and safer instructions that older processors cannot run.
techidream.com
techidream.com › fatal-glibc-error-cpu-does-not-support-x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2 (Fix)
How do I check if my CPU supports x86-64-v2?
Use lscpu, cat /proc/cpuinfo, or Windows tools like CPU-Z to see if you have SSE4.2, AVX, and BMI1.
techidream.com
techidream.com › fatal-glibc-error-cpu-does-not-support-x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2 (Fix)
Which CPUs fully support x86-64-v2 in 2025?
Most Intel 3rd Gen and newer CPUs, and almost all AMD Ryzen processors.
techidream.com
techidream.com › fatal-glibc-error-cpu-does-not-support-x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2 (Fix)
Reddit
reddit.com › r/docker › fatal glibc error: cpu does not support x86-64-v2
r/docker on Reddit: Fatal glibc error: CPU does not support x86-64-v2
May 9, 2024 -
Hi,
I've used docker a little in the past, but am fairly new to using it. I've just been following the basic installation instructions here:
https://www.zabbix.com/documentation/current/en/manual/installation/containers
Which asks to use the following to create the container:
# docker run --name zabbix-server-pgsql -t \
-e DB_SERVER_HOST="postgres-server" \
-e POSTGRES_USER="zabbix" \
-e POSTGRES_PASSWORD="zabbix_pwd" \
-e POSTGRES_DB="zabbix" \
-e ZBX_ENABLE_SNMP_TRAPS="true" \
--network=zabbix-net \
-p 10051:10051 \
--volumes-from zabbix-snmptraps \
--restart unless-stopped \
-d zabbix/zabbix-server-pgsql:alpine-6.4-latest
Sadly the container won't start with the logs showing me this error:
sudo docker logs -f mysql-server
Fatal glibc error: CPU does not support x86-64-v2
It's running on:
cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 36 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
I'm presuming it's an incompatibility with an old cpu....but I'm stuck as to what to do now....
Top answer 1 of 2
5
Nothing. That CPU is way too old (it's from 2007) and the glibc that's included with that docker image is apparently trying to use features your CPU doesn't yet support. Only way around is either a newer CPU, or a different image (older or self-made) that doesn't require that new architecture.
2 of 2
1
bit off-topic as this example is for another db (mysql), but the image: mysql:8.0 threw same errors, then I found this: image: mysql:8.4.0-oraclelinux8 so just for the (mysql) record.
Medium
medium.com › @Derilee › how-to-resolve-fatal-glibc-error-cpu-does-not-support-x86-64-v2-e502712c1abe
How To Resolve Fatal glibc error: CPU does not support x86-64-v2 | by Samuel Victor | Medium
September 1, 2023 - 4. Search for your PC generation among the available options, and choose the one that includes “V2.” For example, if you are using a fifth-generation CPU like the Intel Core Processor (Broadwell) without TSX, select “Intel Core Processor (Broadwell, no TSX) (Broadwell-v2).” · 5. After selecting the appropriate CPU configuration, save your settings. 6. Now, run your Linux OS installation process again. Testing the Solution Upon completing these steps, your Linux OS installation should proceed without encountering the “Fatal glibc error: CPU does not support x86–64-v2” message.
LinuxServer.io
discourse.linuxserver.io › lsio discussion › container support
Fatal glibc error: CPU does not support x86-64-v2 - Container Support - LinuxServer.io
May 11, 2024 - Hi! A Mysql container is throwing this error and doesn’t start: Fatal glibc error: CPU does not support x86-64-v2 It’s running on a Debian 11 server and used together with Piwigo. The cpu seems to support sse2: gustavo@srv2:~/docker/piwigo$ sudo grep -o sse2 /proc/cpuinfo sse2 sse2 The ...
Red Hat
access.redhat.com › solutions › 6833751
RHEL 9 guest panic's during boot with following error "Fatal glibc error: CPU does not support x86-64-v2" - Red Hat Customer Portal
August 27, 2024 - RHEL 9 Virtual Machine fails to boot or to install RHEL 7 and 8 Virtual Machine works on the same platform Fatal glibc error: CPU does not support x86-64-v2 Fatal glibc error: CPU does not support x86-64-v2 [ 12.457752] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
Techidream
techidream.com › fatal-glibc-error-cpu-does-not-support-x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2 (Fix)
February 24, 2026 - The “Fatal glibc error: CPU does not support x86-64-v2″ occurs when your processor lacks the modern instruction sets required by newer Linux systems and applications. Many modern Linux distributions and containers now require x86-64-v2 support, ...
GitHub
github.com › wazuh › wazuh-packages › issues › 3007
Fatal glibc error: CPU does not support x86-64-v2 · Issue #3007 · wazuh/wazuh-packages
June 19, 2024 - Fatal glibc error: CPU does not support x86-64-v2 · This issue appears to be related to an incompatibility between the version of glibc used in our 4.8.0 release and certain older CPUs.
Author wazuh
Reddit
reddit.com › r/centos › fatal glibc error: cpu does not support x86-64-v2
r/CentOS on Reddit: Fatal glibc error: CPU does not support x86-64-v2
July 15, 2024 -
Hello,
I am trying to learn Linux with CentOS and after multiple attempts of installing CentOS Stream 9, I keep getting this error message.
It seems like my hardware is not supported for this version of CentOS. Additionally, when I tried to find other versions of CentOS, it is not available on their website, and the mirror links for the older version (7, 8, and Stream 8) does not load too.
Do you guys have a suggestion for this? I am lost and confused right now. Thanks.
Top answer 1 of 3
4
You're using VirtualBox, and for one reason or another, it is presenting a virtual CPU with reduced functionality to the guest. CentOS Stream 9 and related releases will not run on CPUs (physical or virtual) with reduced functionality. The problem is not your hardware, it's the configuration of VirtualBox. Unfortunately, all of the discussions I can find about enabling modern features are > 10 years old, and I can't find anything in VirtualBox's official documentation. I'm sure a configuration option is there... somewhere. This document suggests the CPU extensions should be enabled by default: https://www.virtualbox.org/manual/ch09.html#sse412passthrough I'd look around more, in that direction
2 of 3
2
UPDATE: I have solved it. I just needed to update the version of my VirtualBox. I didn't realize I was using 6.1 rather than 7.0.
Broadcom
knowledge.broadcom.com › external › article
"Fatal glibc error: CPU does not support x86-64-v2" when updating SMG 10.9.0 to 10.9.1
July 21, 2025 - Fatal glibc error: CPU does not support x86-64-v2 · VMWare virtual infrastruture · The EVC CPU Mode for the VMWare cluster is not set to a cpu generation high enough to support the x86-64-v2 instruction set · If using EVC (Enhanced vMotion Compatibility) on the vSphere cluster that hosts ...
Percona Community
forums.percona.com › percona monitoring and management (pmm) › pmm 2.x
After upgrade, PMM2 container fails to start with "Fatal glibc error: CPU does not support x86-64-v2" - PMM 2.x - Percona Community Forum
July 31, 2023 - Only error msg from “docker logs …” is Fatal glibc error: CPU does not support x86-64-v2 I see there’s a (new?) requirement “Your CPU must support the SSE4.2 instruction set…
Red Hat
access.redhat.com › solutions › 7057314
Running Red Hat Enterprise Linux 9 (RHEL) or Universal Base Image (UBI) 9 container images fail with "Fatal glibc error: CPU does not support x86-64-v2" - Red Hat Customer Portal
When running any container image based on Red Hat Enterprise Linux 9 (RHEL9) or Universal Base Image 9 (UBI9), the following error is printed when starting the container: Fatal glibc error: CPU does not support x86-64-v2 The above error can appear either when running podman commands, or may ...
GitHub
github.com › JATOS › JATOS › issues › 287
Fatal glibc error: CPU does not support x86-64-v2 · Issue #287 · JATOS/JATOS
April 26, 2023 - 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
Author JATOS
Proxmox
forum.proxmox.com › home › forums › proxmox virtual environment › proxmox ve: installation and configuration
issue with running docker container in a vm | Proxmox Support Forum
January 28, 2025 - I created a vm where I want to deploy microservices, when I tried running a container I got this issue Fatal glibc error: CPU does not support x86-64-v2...
TechBloat
techbloat.com › home › fatal glibc error: cpu does not support x86-64-v2
Fatal Glibc Error: CPU Does Not Support X86-64-V2 - TechBloat
May 16, 2026 - A different kernel may help only ... Fatal glibc error: CPU does not support x86-64-v2 means the program, container, VM, or operating system expects a newer x86-64 CPU baseline than the current environment provides....
GitHub
github.com › ansible › awx › issues › 11879
can not update 19.5 -> 20.0 Fatal glibc error: CPU does not support x86-64-v2 · Issue #11879 · ansible/awx
March 9, 2022 - can not update 19.5 -> 20.0 pods does not start due to: kubectl logs --previous awx-whz-6d8f7f4589-sw8rv awx-whz-web -n whz Fatal glibc error: CPU does not support x86-64-v2
Author ansible
Broadcom
knowledge.broadcom.com › external › article › 397953 › rhel-9-guest-panics-during-boot-with-fol.html
RHEL 9 guest panic's during boot with following error "Fatal glibc error: CPU does not support x86-64-v2"
March 27, 2026 - upgrading, installing, or creating a Red Hat VM from a template. The guest OS VM fails during boot with the following error message: "Fatal glibc error: CPU does not support x86-64-v2"
Red Hat
access.redhat.com › solutions › 7000365
[leapp] IPU 8>9: Fatal glibc error: CPU does not support x86-64-v2 - Red Hat Customer Portal
June 13, 2024 - Fatal glibc error: CPU does not support x86-64-v2 Error in PREIN scriptlet in rpm package libutempter Error in POSTIN scriptlet in rpm package p11-kit-trust Error in PREIN scriptlet in rpm package ca-certificates Error in POSTIN scriptlet in ...
GitHub
github.com › wazuh › wazuh-kubernetes › issues › 719
Fatal glibc error: CPU does not support x86-64-v2 using 4.8.0 image · Issue #719 · wazuh/wazuh-kubernetes
June 18, 2024 - Hello everyone I'm using rancher / kubernetes to deploy wazuh environment, using image 4.7.5 works fine but moving the same environment to use image 4.8.0 none of the pods get up (manager, indexer and dashboard image) with this cpu flags...
Author wazuh