All Products
Search
Document Center

Server Migration Center:What do I do if the "Multiple devel kernels installed" error message appears?

Last Updated:May 11, 2024

Problem description

During the migration of an operating system, the "Multiple devel kernels installed" error message is reported.

Cause

A kernel-devel package is used for kernel development. For example, you can use a kernel-devel package to develop kernel modules without the need to use the source code of the kernel. A kernel-devel package provides sufficient kernel header files and Makefiles to build modules based on the kernel package. When you develop kernel modules, you need to only reference the corresponding kernel header files in this package. You need to install kernel-devel packages only in a development environment in which you want to develop and compile kernel programs of the corresponding versions. The development environment is not affected if you uninstall the kernel-devel packages. The dnf command does not support in-place upgrade for multiple kernel-devel packages. If multiple kernel-devel packages are installed, the operating system may fail to be migrated.

Solution

  1. Connect to the Elastic Compute Service (ECS) instance whose operating system you want to migrate. For more information, see Connect to a Linux instance by using a password or key.

  2. Delete the unnecessary kernel-devel packages to retain only one kernel-devel package.

    1. Run the following command to view the installed kernel-devel packages:

      rpm -qa | grep kernel-devel

      The names and versions of all kernel-devel packages installed in your operating system are displayed:

      kernel-devel-3.10.0-1160.90.1.el7.x86_64
      kernel-devel-3.10.0-1160.80.1.el7.x86_64
    2. Run the following command to delete the unnecessary kernel-devel packages to retain only one kernel-devel package:

      yum remove kernel-devel-3.10.0-1160.80.1.el7.x86_64
    3. Enter y and press the ENTER key to confirm the deletion.

  3. After the error is resolved, run the SMC client and retry the migration job. For more information, see Run the SMC client.