Can your VPS run AlmaLinux 10 or Rocky 10?
AlmaLinux 10 and Rocky 10 need an x86-64-v3 CPU by default. Two commands run inside your VPS tell you if its virtual CPU qualifies, and what to do if not.
The short answer
Your VPS can run Rocky Linux 10 or the standard build of AlmaLinux 10 only if its virtual CPU reaches the x86-64-v3 level. To find out, run /lib64/ld-linux-x86-64.so.2 --help | grep x86-64 inside the VPS. If the x86-64-v3 line ends in (supported, searched), the standard builds of both releases will run. If it does not, Rocky 10 is out. AlmaLinux 10 is still possible, but only from its separate x86_64_v2 build.
Run the check inside the VPS. Do not trust a spec sheet for this. The physical server can be new enough while the CPU your VPS sees is not, because the hypervisor decides which CPU features each guest is shown. This guide covers what the levels mean, the two checks, why a VPS can report less than its hardware, and the ways forward when v3 is missing.
What x86-64-v2 and x86-64-v3 mean
An x86-64 microarchitecture level is a named set of CPU instructions. The levels are defined in the x86-64 psABI (processor-specific application binary interface). That is the document compilers and the dynamic linker follow on 64-bit Intel and AMD systems. A distribution built for a level is free to use every instruction in that level. That means the CPU must have all of them, not most of them.
There are four sets. The psABI says they are cumulative, so each level includes everything below it.
- Baseline x86-64: CMOV, CX8, FPU, FXSR, MMX, OSFXSR, SCE, SSE, SSE2. This is the starting set.
- x86-64-v2 adds CMPXCHG16B, LAHF-SAHF, POPCNT, SSE3, SSE4_1, SSE4_2 and SSSE3. In plain terms, this is the SSE4.2 and POPCNT generation. SSE means Streaming SIMD Extensions.
- x86-64-v3 adds AVX, AVX2, BMI1, BMI2, F16C, FMA, LZCNT, MOVBE and OSXSAVE. This is the AVX2 generation. AVX means Advanced Vector Extensions, BMI means bit manipulation instructions, and FMA means fused multiply-add.
- x86-64-v4 adds AVX512F, AVX512BW, AVX512CD, AVX512DQ and AVX512VL.
The psABI adds one condition for v3 and v4. Those levels count only if their features are fully enabled, and that check includes the XCR0 register. A CPU that has AVX is not enough on its own. The operating system must also enable XSAVE, the mechanism that saves the larger AVX registers. OSXSAVE in the v3 list is the flag that says this was done.
To put real chips on the scale, Rocky's 10.0 release notes say x86-64-v3 is based on the feature set of the Intel Haswell generation. They also say AMD processors older than the Excavator architecture may not be fully supported, and they name some Intel Atom parts, Parker Ridge and the Elkhart Lake x6416RE, as not supported. A generation name tells you what the hardware can do. It does not tell you what your VPS is shown. That is why the checks below run inside the guest.
Check 1: ask the glibc dynamic loader
The dynamic loader is the program that starts every dynamically linked binary on the system. It already has to know which levels the CPU supports, because it picks optimized library builds from per-level directories called glibc-hwcaps. glibc 2.33 added a --help option to the loader that prints this list. On x86-64 Linux the loader lives at /lib64/ld-linux-x86-64.so.2.
ldd --version | head -n 1
/lib64/ld-linux-x86-64.so.2 --help | grep x86-64The first command prints your glibc version. If it is older than 2.33, the loader has no glibc-hwcaps list to show, so use the second check below and ask your provider instead.
In the full --help output, the list sits under the heading Subdirectories of glibc-hwcaps directories, in priority order:. The grep keeps only the level lines. There is one line per level, and the highest level comes first. Each line ends in one of three ways, and glibc's source code defines all three:
(supported, searched): the CPU, as the loader sees it, has this level, and the loader searches that directory.(supported, masked): the CPU has the level, but this loader has been set not to search that directory.- No tag after the level name: the CPU, as the loader sees it, does not have this level.
The line that matters is x86-64-v3. Rocky's CPU compatibility guide puts the rule plainly: if (supported, searched) is missing next to the x86-64-v3 entry, the CPU is not compatible with Rocky Linux 10. The same guide adds that (supported, searched) on the x86-64-v4 line means the CPU is well supported for future versions.
Do not compare your output against a sample from another machine. The result depends on the CPU model your VPS is given, so two virtual machines on the same physical server can print different lines.
Check 2: a quick look at /proc/cpuinfo
The kernel lists CPU flags in /proc/cpuinfo. One grep tests for the best-known v3 feature:
grep -m1 -o -w avx2 /proc/cpuinfoIt prints avx2 if the kernel reports the flag, and nothing if it does not. The file holds one block per logical CPU, and -m1 stops at the first match, so you get one line and not one per core.
Treat this as a hint, not a verdict. The kernel documentation says the flags show features the kernel has enabled and supports, and that the list is not complete. It also says AVX flags will not show up if the XSAVE feature is disabled, because they depend on it. AVX2 is one feature out of nine in the v3 list, and the loader checks all of them. The kernel documentation itself tells applications to use the glibc facilities for querying CPU support. Check 1 is that facility, so its answer wins.
Why your VPS can report less than its physical CPU
A KVM virtual machine does not see the host processor directly. The hypervisor presents a CPU model to the guest, and that model decides which feature flags the guest kernel and glibc can find. If the model leaves out AVX2, the guest has no AVX2, whatever the chip in the rack can do.
QEMU, the emulator behind most KVM setups, shows the choice clearly. With no -cpu argument, QEMU gives an x86_64 guest the qemu64 model. Its documentation says the default models are designed so they can run on all hosts. It also says the models it does not recommend expose a very limited featureset, which prevents guests from having optimal performance. QEMU's CPU page includes a table mapping its named CPU models to the ABI levels baseline, v2, v3 and v4.
The other end is -cpu host, which passes the host CPU model and features exactly to the guest. QEMU's documentation warns that live migration is unsafe in this mode. That is the reason a provider might not use it. A provider that moves running VMs between hosts with different processors has a reason to present a common, smaller model, and that model can sit below v3 on hardware that is well above it.
This is the same mechanism that hides AES-NI from some guests, and checking for AES-NI on a VPS and getting it restored walks through it from the encryption side. Two more commands help you describe your VPS to your provider:
systemd-detect-virt
lscpu | grep -i 'model name'systemd-detect-virt prints the virtualisation type, such as kvm. lscpu prints the CPU model name the guest is shown. If the first command names a container technology, your system shares the host's kernel and there is no virtual CPU model at all. How KVM, Xen and LXC virtualisation differ explains what that changes.
Which releases need x86-64-v3
AlmaLinux 10. AlmaLinux's post of 20 November 2026 says AlmaLinux OS 10 is built for the x86_64_v3 architecture level by default. The same post says AlmaLinux also provides a parallel x86_64_v2 build for older hardware. The 10.0 release notes describe that v2 build as being ONLY for older hardware, in capitals. AlmaLinux's launch post of 27 May 2025 says the project followed Red Hat's decision to ship x86-64-v3 optimized binaries by default. It also said users on older hardware would continue to receive security updates for another 10 years. The naming varies between AlmaLinux pages: the blog and the download paths write x86_64_v2, while the wiki release notes write x86-64-v2. Both mean the same level.
Red Hat Enterprise Linux 10. Red Hat's architecture pages for RHEL 10.2 and 10.3 list AMD and Intel 64-bit at a minimum of x86-64-v3. A CPU at v2 is below that minimum.
Rocky Linux 10. The Rocky Linux 10.3 announcement of 16 November 2026 says Rocky Linux 10 requires the x86-64-v3 microarchitecture level on 64-bit AMD and Intel systems, so hardware at x86-64-v2 and earlier is not supported. The 10.0 announcement of 11 June 2025 called the removal of x86-64-v2 support the most significant change in Rocky Linux 10. Rocky 10.3 is published for x86-64-v3, aarch64, riscv64, ppc64le and s390x. The Rocky 9.9 announcement of the same day lists x86-64-v2 among its architectures.
Ubuntu. The release notes for Ubuntu 24.04 and 26.04 state no x86-64 level for the default amd64 install. Ubuntu 26.04 LTS, released 23 April 2026, carries amd64v3, a package variant built for x86-64-v3 that was added in Ubuntu 25.10. Its release notes say the variant is opt-in by default for maximum compatibility. They also say that on all cloud providers, AMD64 images are now built with AMD64v3 by default. Canonical's announcement of the variant warns that after you install the v3 packages, you cannot move the disk to an older machine without x86-64-v3.
Debian. The Debian 13 installation guide says Debian does not impose hardware requirements beyond those of the Linux kernel and the GNU tool-sets. Neither that guide nor the amd64 ports page names a v2 or v3 level. A Debian wiki page proposes architecture variants such as amd64v3 without raising the baseline, but it is a proposal.
If you are picking a release from scratch and your CPU falls short, choosing the right OS for your VPS covers the wider trade-offs.
What to do if your VPS lacks x86-64-v3
There are four realistic paths. Which one fits depends on the distribution you run now and how much your provider can change.
Install the AlmaLinux 10 x86_64_v2 build. It is a full AlmaLinux 10 release built for the older level. The images are on AlmaLinux's download page, under the section for AlmaLinux OS 10 x86_64 v2: almalinux.org/get-almalinux. On a VPS you usually install from your provider's image list or a custom ISO upload, so check which of the two your provider supports. This is now a real difference between the two distributions on older hardware, next to the others in Rocky Linux vs AlmaLinux.
Stay on release 9 for now. Rocky Linux 9.9 is published for x86-64-v2, so a v2 VPS can keep running a supported Rocky release. While you stay, keep it patched. Applying only security updates with dnf keeps the patch flow small on a server you do not want to change much.
Ask your provider about the CPU model. You cannot change the CPU model from inside the guest. The hypervisor sets it. Send your provider the output of the loader check and the lscpu model name line. Then ask a direct question: does any host or plan present a CPU model that reaches x86-64-v3? Run the loader check again after any change they make, because the answer is the line it prints, not the plan name.
Upgrade AlmaLinux 9 in place with ELevate. On 20 November 2026, AlmaLinux announced ELevate upgrade paths from AlmaLinux OS 9 to AlmaLinux OS 10 x86_64_v2, and from AlmaLinux OS 9 to AlmaLinux OS Kitten 10 x86_64_v2. The same release adds upgrades from the installation ISO, for systems with no internet access. The announcement names EPEL (Extra Packages for Enterprise Linux) as the third-party repository currently supported on these paths. The source system must be AlmaLinux 9, so a Rocky 9 server is not on these listed paths. The v2 package names and steps are on AlmaLinux's ELevate wiki page: wiki.almalinux.org/elevate. An April 2026 announcement of the first v2 test builds told readers not to use them on production machines, so read the current status on that page before you upgrade a server that matters. For the regular v3 path on capable hardware, see upgrading AlmaLinux 9 to 10 with ELevate.
FAQ
How do I check if my CPU supports x86-64-v3 on Linux?
Run /lib64/ld-linux-x86-64.so.2 --help | grep x86-64. This needs glibc 2.33 or later. If the x86-64-v3 line ends in (supported, searched), the CPU as the system sees it has every v3 feature. A line with no tag after the level name means that level is not available. grep -m1 -o -w avx2 /proc/cpuinfo is a faster hint, but it tests only one of the nine v3 features, so the loader check is the one to trust.
Why does my VPS not show AVX2 when the physical CPU has it?
The hypervisor chooses the CPU model your VPS sees, and a generic model leaves out newer features. QEMU's default qemu64 model is designed to run on all hosts, so it exposes a limited feature set. -cpu host passes the real features through, but QEMU warns that live migration is unsafe in that mode. That is why some providers use a smaller common model. Only your provider can change it.
Does Rocky Linux 10 have an x86-64-v2 build?
Rocky's 10.0 and 10.3 announcements list none. The 10.3 announcement of 16 November 2026 says Rocky Linux 10 requires x86-64-v3 and that hardware at x86-64-v2 and earlier is not supported. On a v2 machine, the options are Rocky Linux 9, which is published for x86-64-v2, or AlmaLinux 10's separate x86_64_v2 build.
Can I upgrade AlmaLinux 9 to AlmaLinux 10 on a CPU without x86-64-v3?
Yes, to the x86_64_v2 build. On 20 November 2026 AlmaLinux announced an ELevate path from AlmaLinux OS 9 to AlmaLinux OS 10 x86_64_v2, with EPEL as the supported third-party repository. The package names and steps are on AlmaLinux's ELevate wiki page. An earlier test release in April 2026 was marked as not for production, so check the current status there before you upgrade a production server.