Rocky Linux 10 Tutorial / Check CPU compatibility and verify the installation ISO

To install the x86_64 image of Rocky Linux 10, the CPU and virtual CPU must meet the x86-64-v3 requirements. Once you have received the ISO, verify that the file content matches using the SHA-256 checksum, and use GNU Privacy Guard (GnuPG, invoked as gpg) to verify the signature on that checksum. Drawing the conclusion that the file is official based only on checksum match skips one verification step.

A 64-bit CPU does not necessarily support x86-64-v3

x86_64 represents the Intel and AMD 64-bit architecture, while x86-64-v3 is the required instruction set level within that architecture. The official x86_64 build of Rocky Linux 10 requires v3 level. The fact that 64-bit Windows or Rocky Linux 9 ran on an older PC alone does not mean you can install 10.

Official Hardware Requirements explains AVX, AVX2, BMI1/2, FMA, etc. Instead of assuming compliance just by looking at the CPU product name or a single AVX entry, check the CPU’s full supported features and virtualization settings. On ARM devices, review the supported aarch64 image and virtualization environment instead of the x86_64 image.

In virtual machines, the features provided by the physical CPU and those actually seen by the guest may differ. Check the virtualization program version, CPU compatibility mode, and feature exposure settings. The host and guest architectures must also match. Missing required features cannot be fixed by simply re-downloading the ISO checksum.

On an existing Linux system, you can investigate the model and feature list with lscpu, but seeing a specific feature in the output does not fully verify v3 support. You need to verify boot results on the console of the target VM. If a CPU requirements error occurs immediately after boot, investigate the CPU and virtualization settings before repeating the installation.

Which image should I download: boot, minimal, or dvd?

For the first server lab, a small installation makes it easier to track what you add later. This example uses a minimal ISO for the x86_64 environment. An ISO is an image that bundles the contents of the installation media into a single file, and you should check the version, architecture, and type included in the name together.

Type Selection criteria Conditions to check
boot When using network installation sources during the installation process Network and repository access must be available even during installation
minimal When installing a basic server and adding only necessary packages Repository access is needed for updates and additional packages after the installation
dvd When you want to include more installation packages in the media Check download size and required installation profile

Check the current files in the official 10 series x86_64 ISO directory. The example below uses Rocky-10.2-x86_64-minimal.iso verified on November 12, 2026. When a new minor release is released later, all ISO, checksum, and signature files must be replaced with the same version. latest aliases may point to different files, so it is better to record the actual version name for verification history.

Prepare ISO, checksum, signature, and public key

Create a separate working folder and prepare the following files. Files with ISO and the suffixes .CHECKSUM and .CHECKSUM.asc should be downloaded in the same directory. The public key should be obtained from the official site for version 10.

  • Rocky-10.2-x86_64-minimal.iso: Installation image
  • Rocky-10.2-x86_64-minimal.iso.CHECKSUM: Official SHA-256 value
  • Rocky-10.2-x86_64-minimal.iso.CHECKSUM.asc: Detached signature of the above checksum file
  • RPM-GPG-KEY-Rocky-10: Public key to use for signature verification

You can also save the file link from the browser. If you use curl on Linux, you can receive it like the following by putting the file name in a variable. First, check that there is no file with the same name in the current folder before running. ISO downloads require about 2GB of storage space and transfer, and the file size varies depending on the version.

mkdir rocky-iso-check
cd rocky-iso-check
base='https://download.rockylinux.org/pub/rocky/10/isos/x86_64'
iso='Rocky-10.2-x86_64-minimal.iso'
curl -fLO "$base/$iso"
curl -fLO "$base/$iso.CHECKSUM"
curl -fLO "$base/$iso.CHECKSUM.asc"
curl -fLO 'https://download.rockylinux.org/pub/rocky/RPM-GPG-KEY-Rocky-10'

-f prevents HTTP error responses from being treated as successful downloads. If any command fails, do not proceed to the next step; check the URL, network, and remaining space. Also, check if the browser appended (1) to the file name or saved an HTML error page.

Compare the public key fingerprint and verify the checksum signature.

The gpg command of GnuPG is required. On existing Linux systems, use the GnuPG package provided by your distribution; on Windows, prepare the GnuPG tools from a trusted source. First, display the fingerprint before importing the key.

gpg --show-keys --with-fingerprint RPM-GPG-KEY-Rocky-10

The fingerprint is a long value that identifies the key. Do not trust only the name on the downloaded key; compare it with the fingerprint and full value of the Rocky Linux 10 official release key guided by Rocky Linux Official GPG Key Instructions. The values published at the time of verification are as follows.

FC22 6859 C086 0BF0 DDB9 5B08 5B10 6C73 6FED FC85

If the full fingerprint matches, import the public key and specify the detached signature and checksum file together. Do not use the test release key or the key for 9 instead.

gpg --import RPM-GPG-KEY-Rocky-10
gpg --verify Rocky-10.2-x86_64-minimal.iso.CHECKSUM.asc Rocky-10.2-x86_64-minimal.iso.CHECKSUM

After successful verification, look for the Good signature message that the signature is correct. The output language and detailed wording may vary depending on the environment. No public key means the required key is missing, and BAD signature means the signature could not be verified with that key. In this case, do not proceed with the installation and check the combination of key, signature, checksum, and the download status.

Immediately after obtaining the key, a warning may appear that the key is not guaranteed through a trusted certification path. Whether the cryptographic signature is correct and whether you can trust the key owner are separate judgments. Do not arbitrarily raise the key trust level to maximum to remove the warning; perform official fingerprint verification instead.

The source lesson’s signing check on November 12, 2026 used GnuPG 2.4.9 included in Git for Windows on Windows and in a separate working key repository. The official checksum was verified with the signature, and the comparison file with altered checksum content was rejected due to signature mismatch. This check applies to the checksum file and does not mean that the entire ISO download or native Rocky Linux execution has been verified.

Compare with the actual ISO's SHA-256 value

The signature is the step that verifies the origin of the checksum. Now you need to check whether the content of the ISO you received matches that value. On Linux, run it in the folder where the ISO and checksum file are located.

sha256sum -c Rocky-10.2-x86_64-minimal.iso.CHECKSUM

OK should appear after the corresponding ISO name. An error saying that the file does not exist means you should check the current folder, name, and extension, while FAILED investigates possibilities such as an incorrect version of the checksum, interrupted download, or file modification. Do not use a failed ISO for installation. Official installation guides also explain checksum verification to confirm integrity in this manner.

In Windows PowerShell, calculate SHA-256 with the command below. Compare the resulting Hash value with the 64-character value in the checksum file. Differences in uppercase and lowercase letters do not indicate a difference in hash values.

Get-FileHash -Algorithm SHA256 -LiteralPath '.\Rocky-10.2-x86_64-minimal.iso'
Get-Content -LiteralPath '.\Rocky-10.2-x86_64-minimal.iso.CHECKSUM'

The fact that file names are the same or sizes are similar does not replace SHA-256 matching. Connect files for which both signature verification and ISO hash comparison are complete to the VM. If a boot menu is provided to check the installation media itself, use it as well, but that media check is not a substitute for comparing official key fingerprints.

Troubleshoot the step that failed

  • Download failed: Check storage, URL, and network first, and distinguish between incomplete files and completed files.
  • Fingerprint mismatch: Recheck the key file and official instructions. Do not trust a key that matches only part of the fingerprint.
  • Signature failure: Verify that you have received checksums and signatures of the same version, architecture, and ISO type.
  • ISO hash mismatch: Compare the version and file name and re-download the corrupted ISO. Do not modify the expected checksum to fit your file.
  • Verification passed but boot failed: Check CPU features, virtual CPU exposure, architecture, firmware, and virtualization program settings. File integrity and execution compatibility are separate issues.

Leave in the verification record the actual file name of the ISO, checksum value, compared public key fingerprint, and signature result. This becomes a record that can explain “which installation file was trusted and used” when recreating the same VM later.