For some use cases, you may wish to run a custom-compiled Linux kernel on your Linode. This can be useful if you need to enable certain kernel features that are unavailable in Linode-supplied or distribution-supplied kernels, or when you want to disable features that are compiled into such kernels. For example, some users may desire SELinux support, which is not enabled in stock Linode kernels, and may not be enabled in some distribution-supplied kernels.
If you'd rather run a distribution-supplied kernel instead, please follow our guide for running a distribution-supplied kernel. Before proceeding with these instructions, you should follow the steps outlined in our getting started guide. After doing so, make sure you are logged into your Linode as the "root" user via an SSH session.
Issue the following commands to update your package repositories and installed packages, install development tools required for compiling a kernel, and install the ncurses library.
Ubuntu and Debian:
apt-get update apt-get upgrade --show-upgraded apt-get install -y build-essential libncurses5-dev
CentOS and Fedora:
yum update yum install -y ncurses-devel make gcc
pacman -Syu pacman -Sy base-devel ncurses
If this is the first time you've compiled a kernel on your Linode, issue the following command to remove any existing files in the /boot directory. This helps avoid confusion later, as certain distributions elect to install a pre-compiled kernel package along with their development packages.
rm -rf /boot/*
Your kernel must be properly configured to run under our environment. Some required configuration options may include:
It is recommended that you start with a kernel config from a running Linode kernel. All Linode kernels will expose their configuration via /proc/config.gz. For example:
zcat /proc/config.gz > .config make oldconfig
make oldconfig will prompt you to answer any new configuration options not present in the old configuration file.
Changes to the kernel's configuration can be made with the menuconfig command. Enable any additional options you require, making sure to leave ext3 filesystem support compiled into the kernel (not configured as a module). For example, to enable SELinux support, check the option "Security options --> NSA SELinux Support" in the configuration interface.
Once your configuration options are set, exit the configuration interface and answer "y" when asked whether you would like to save save your new kernel configuration.
Issue the following commands to compile and install the kernel and modules:
make -j3 bzImage make -j3 modules make make install make modules_install
If you're running Arch Linux, issue the following command to give the kernel a more descriptive name. Modify the command as necessary to reflect the kernel version you've just compiled.
mv /boot/vmlinuz /boot/vmlinuz-18.104.22.168-custom
PV-GRUB will always look for menu.lst in the directory /boot/grub. Create this directory with the following command:
Create a menu.lst file with the following contents. Adjust the "title" and "kernel" lines to reflect the actual filenames found in the /boot directory.
timeout 5 title Custom Compiled, kernel 22.214.171.124-custom root (hd0) kernel /boot/vmlinuz-126.96.36.199-custom root=/dev/xvda ro quiet
Note that there is no initrd line. With some distributions, the initrd image prepared during the kernel installation process will not work correctly with your Linode, and it isn't needed anyhow.
In the Linode Manager, edit your Linode's configuration profile to use either pv-grub-x86_32 or pv-grub-x86_64 as the "Kernel", depending on the version of Fedora you have deployed (32-bit or 64-bit). Make sure the root device is specified as xvda. Save your changes by clicking "Save Profile" at the bottom of the page, and reboot your Linode from the "Dashboard" tab.
Once your Linode has rebooted, log back into it and issue the command "uname -a". You should see output similar to the following, indicating you're running your custom kernel:
Linux li175-165 188.8.131.52-custom #1 SMP Sat Jul 17 17:09:58 EDT 2010 i686 i686 i386 GNU/Linux
Note that if you install an updated kernel, you'll need to add an entry for it to your menu.lst file. By default, the first kernel in the list will be booted. If you have multiple kernels installed, you can choose which one your Linode uses to boot by watching for the kernel list in the Lish console (see the "Console" tab in the Linode Manager). Congratulations, you've booted your Linode using a custom-compiled kernel!
This guide is licensed under a Creative Commons Attribution-NoDerivs 3.0 United States License.
Last edited by Matthew Cone on Wednesday, December 5th, 2012 (r3263).