Build Linux kernels for Arm cloud instances
Introduction
Set up your Arm instance for kernel building
Build and install custom Linux kernels
Build kernels for Fastpath validation
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Advanced
Reading time:  1 hr
Last updated:  17 Sep 2026
Skill level:
  Advanced
Reading time:
  1 hr
Last updated:
  17 Sep 2026
Author:Geremy Cohen, Arm
Arm IP:Neoverse
Tags: Performance and Architecture AWS Graviton Microsoft Azure Cobalt Google Axion Oracle Cloud Infrastructure (OCI) Ampere Compute Linux TuxMake
Author:
  • Geremy Cohen, Arm
Arm IP:
Neoverse
Tags:
Performance and Architecture AWS Graviton Microsoft Azure Cobalt Google Axion Oracle Cloud Infrastructure (OCI) Ampere Compute Linux TuxMake

Who is this for?

This is an advanced topic for software developers building custom Linux kernels on Arm servers and cloud instances.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Set up a build environment for compiling Linux kernels on Arm cloud instances.
  • Build custom Linux kernels with various configurations using TuxMake.
  • Install and verify custom-built kernels.
  • Configure kernels for specific use cases, including 64 KB page sizes and Fastpath testing.

Prerequisites

Before starting, you'll need the following prerequisites:

  • An Arm cloud instance with at least 24 vCPUs and 200 GB of free storage running Ubuntu 24.04 LTS
  • Understanding of kernel images and modules
  • Familiarity with GRUB bootloader and initramfs

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll prepare an Arm-based cloud instance running Ubuntu, and use TuxMake to compile custom Linux kernels with selectable versions and configurations. First, you’ll choose between installing a kernel directly and generating packages, then verify the bootloader, modules, and build artifacts. You can configure 64 KB pages or create Fastpath-ready, build-only outputs, copying the flat artifacts to a test environment for validation.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I choose the kernel version tag when building with TuxMake?
The examples use valid Linux version tags such as v6.18.1, but you can select any other valid tag. Pass your chosen tag to the --tags flag and TuxMake builds that version.
What result should I expect after installing a custom kernel?
You should see a new GRUB entry for the installed kernel. After reboot, the running kernel version should match the one you built, and the corresponding modules should be available.
What should I check if my build is very slow or runs out of memory?
Use a sufficiently large Arm instance, as smaller instances take longer and can run out of memory during compilation. Confirm that you have ample free storage before starting the build.
Can I combine --fastpath true with --kernel-install?
No. Fastpath is a build-only workflow, so don’t combine --fastpath true (or its demo shortcut) with --kernel-install or any --install-from commands. Build the kernel, then copy the flat artifacts to your test environment.
Which workflow should I use if I want packages instead of installing directly?
Run ./scripts/kernel_build_and_install.sh --tags v6.18.1 --include-bindeb-pkg to produce Debian packages alongside the flat kernel artifacts. The .deb files are written under ~/kernels/v6.18.1 for later transfer and installation.
Next