criu is an utility to checkpoint/restore a process tree. This page describes manual installation.
|Note: Most probably you don't need manual installation, but rather Packages for your distro.|
Get the latest release:
|Version:||3.16.1 "Petrified Puffin"|
|Released:||14 Oct 2021|
Alternatively, use git.criu.org git repository. Clone this repo to test new functionality.
Before building, make sure you have C bindings for Google's Protocol Buffers installed. In an RPM-based world this is the
protobuf-c-devel package, and on Debian and derivatives,
If for some reason there is no appropriate package for your system available, just install Google's Protocol Buffer from the
source tarball. The protocol buffer library can be found at http://code.google.com/p/protobuf/, while
protocol buffer C binding can be found at http://code.google.com/p/protobuf-c/.
make in the sources root. Please note that the tool only supports x86_64 and ARM architectures.
Linux kernel v3.11 or newer is required, with some specific options set. If your distribution does not provide needed kernel, you might want to compile one yourself. Note we also have our custom kernel, which might contain some experimental CRIU related patches.
Note you might have to enable
- General setup -> Configure standard kernel features (expert users)
option, which depends on
- General setup -> Embedded system
(welcome to Kconfig reverse chains hell).
The following options should be enabled for CRIU to work:
- General setup -> Checkpoint/restore support
- General setup -> Namespaces support
- General setup -> Namespaces support -> PID namespaces
- General setup -> open by fhandle syscalls
- General setup -> Enable eventfd() system call
- General setup -> Enable eventpoll support
- File systems -> Inotify support for userspace
- Executable file formats -> Emulations -> IA32 Emulation
- Networking support -> Networking options -> Unix domain sockets -> UNIX: socket monitoring interface
- Networking support -> Networking options -> TCP/IP networking -> INET: socket monitoring interface
- Networking support -> Networking options -> TCP/IP networking -> INET: socket monitoring interface -> UDP: socket monitoring interface
- Networking support -> Networking options -> Packet socket -> Packet: sockets monitoring interface
- Networking support -> Networking options -> Netlink socket -> Netlink: sockets monitoring interface
- Processor type and features -> Track memory changes
The iproute2 tool version 3.5.0 or higher is needed for dumping network namespaces.
The latest one can be cloned from iproute2. It should be compiled and a path to ip written in the environment variable
Checking how it works
First thing to do is to run
# criu check --ms
At the end it should say "Looks OK", if it doesn't the messages on the screen explain what functionality is missing.
If you're using our custom kernel, then the
--ms option should not be used, in this case CRIU would
check for all the kernel features to work.
You can then try running the ZDTM Test Suite which sits in the