Updated: 16 November 2026 · Applies to: Linux kernels in current distributions (AlmaLinux, Rocky Linux, CloudLinux, Ubuntu, Debian)

Processes called [migration/0], [migration/1] and so on are kernel threads, not programs someone started. The kernel creates one for every CPU (or vCPU) the server has, and they are normal: you do not need to stop them, and you cannot. A server with 16 CPUs shows 16 of them.

What they do

Each migration/N thread is the "CPU stopper" for CPU number N. In the current kernel source (kernel/stop_machine.c), these threads are created per CPU with the name migration/%u and registered as the scheduler's stop task, which is the highest priority task on that CPU. The kernel uses them when it must run something on a specific CPU with nothing else in the way:

  • moving a running process from one CPU to another, for example to balance load or when a process's CPU affinity changes;
  • short "stop machine" operations, such as taking a CPU offline.

Most of the time they sleep and use no CPU at all.

Why the name is in square brackets

The full command column of ps aux and top shows a name in brackets when the process has no command line, which is the case for kernel threads (according to the ps manual: "ps will instead print the executable name in brackets"). So [migration/3], [kworker/0:1] or [ksoftirqd/2] are all kernel threads, not user programs.

Check that the count matches your CPUs

Count the CPUs the kernel sees:

nproc --all

Count the migration threads:

ps -e -o comm= | grep -c '^migration/'

The two numbers are normally the same. To see each thread with the CPU it belongs to:

ps -eo pid,psr,comm | grep migration

The PSR column shows the processor each thread is bound to; each one stays on its own CPU.

When to look closer

The migration threads themselves are not a problem. If top shows one of them using noticeable CPU for a long time, it is a sign that the kernel is moving work between CPUs very often, and the cause is elsewhere: look at what the busy user processes are and how the load is spread. How to Check CPU Usage on Linux: top, htop, mpstat and sar shows how to find them, and ps Command Examples for Linux Process Monitoring explains the ps options used above.

On CloudLinux you may also see other kernel threads that belong to its resource limits; lve_zombi kernel threads appear. What are they? covers one of them.

Official documentation: Linux kernel source, kernel/stop_machine.c and ps manual page.

Related services

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Unmanaged dedicated servers

full root access and free IPMI KVM, with Free Basic Managed Support.

Managed dedicated servers

our engineers look after the server for you, from $135 a month.

Was this answer helpful?

Still stuck? Open a ticket