Skip to content
Search RunEntLinux

Searches general documentation on RunEntLinux. Each distribution has its own documentation search.

    Browse this documentation

    EL 10: x86-64-v3 baseline

    EL 10’s x86_64 builds raise the minimum microarchitecture baseline to x86-64-v3, roughly Intel Haswell / AMD Excavator from 2013. Physical machines older than that — and VMs using outdated CPU models — cannot install or boot EL 10. AlmaLinux 10 additionally offers a v2 build as the official fallback for older hardware.

    The x86-64 microarchitecture levels are how a distribution states its minimum instruction-set requirement:

    LevelRepresentative instructionsRough hardware era
    v1base x86-642003+
    v2SSE4.2, SSSE3, POPCNT~2008 (Nehalem)
    v3AVX2, BMI1/BMI2, F16C, MOVBE~2013 (Haswell)
    v4AVX-512~2015 (Skylake-SP)

    EL 8’s baseline was v1, EL 9 moved to v2, and EL 10 moves to v3. Raising the baseline lets compilers use the newer instructions across the entire distribution (vectorization, faster string and crypto primitives); the price is dropping older CPUs.

    Releasex86_64 baselineNotes
    EL 8v1
    EL 9v2see EL 9: x86-64-v2 baseline
    EL 10v3RHEL 10 ships v3 only; AlmaLinux 10 also provides a v2 build
    • Physical machines: server CPUs from 2013 on almost always qualify; confirm with the commands below.
    • Virtual machines: the most common trap. Hypervisor defaults such as qemu64 or Nehalem do not satisfy v3; installing EL 10 in such a VM ends in installer crashes or illegal instruction at boot. Set the CPU model to Haswell or newer, or use host-passthrough.
    • AlmaLinux users: the project publishes x86-64-v2 images and repositories for older CPUs; RHEL 10 and Rocky Linux 10 offer no v2 fallback.
    Look for the key v3 instructions
    grep -o -m1 -E 'avx2|bmi2|f16c|movbe' /proc/cpuinfo | sort -u
    lscpu | grep -i 'flags' | tr ' ' '\n' | grep -cE '^(avx2|bmi1|bmi2|f16c|movbe)$'

    Having all five key flags (avx2, bmi1, bmi2, f16c, movbe) means v3 is satisfied. In VMs also check the CPU model the hypervisor exposes:

    Inspect a libvirt VM's CPU model
    sudo virsh dumpxml <vm> | grep -A2 '<cpu'