(Redirected from CR tools)
Jump to: navigation, search

criu is an utility to checkpoint/restore a process tree. This page describes how to manually build and install prerequisites and the tool itself.

Note.svg Note: Most probably you don't need manual installation, but rather Packages for your distro.


[edit] Obtaining CRIU Source

You can download the source code as a release tarball or sync the git repository.

Released: 18 Jun 2014
Changes: git commit v1.3-rc2

git clone git://
cd criu

[edit] Dependencies

[edit] Compiler and C Library

For native compilation on Debian based systems, install the build-essential package. For cross compiling for ARM and AArch64, the Linaro prebuilt toolchains are a good choice. Installing them is described below.

mkdir deps
cd deps
tar --strip=1 -xf gcc-linaro-arm-linux-gnueabihf-4.9-2014.06_linux.tar.xz
tar --strip=1 -xf gcc-linaro-aarch64-linux-gnu-4.9-2014.06-02_linux.tar.xz
cd ..

[edit] Protocol Buffers with C Bindings

CRIU uses the C language bindings of Google Protocol Buffers for serialization. The protoc tool is required at build time and is required at build time and at run time, assuming dynamic linking.

[edit] Distribution Packages

The easiest approach for most would be to install distribution packages. RPM package names: protobuf-c-compiler, protobuf-c-devel. Debian package names: protobuf-c-compiler, libprotobuf-c0-dev.

[edit] Building Protocol Buffers From Source

If you would like to build from source, you can use the following commands to obtain the source code repositories, configure, and build the code.

[edit] Native protobuf
cd deps
git svn clone protobuf
cd protobuf
./configure --prefix=`pwd`/../`uname -m`-linux-gnu
make install
cd ../..
[edit] Native protobuf-c
cd deps
git svn clone protobuf-c
cd protobuf-c
mkdir ../pbc-`uname -m`
cd ../pbc-`uname -m`
../protobuf-c/configure --prefix=`pwd`/../`uname -m`-linux-gnu \
  CPPFLAGS=-I`pwd`/../`uname -m`-linux-gnu/include \
  LDFLAGS=-L`pwd`/../`uname -m`-linux-gnu/lib \
  PATH="`pwd`/../`uname -m`-linux-gnu/bin:$PATH"
# Ignore test-full.proto: "foo.VALUE_B" uses the same enum value as "foo.VALUE_A" messages
make install
# Ignore test-full.proto: "foo.VALUE_B" uses the same enum value as "foo.VALUE_A" messages
cd ../..
[edit] Cross Compiling for ARMv7

If you would like to cross-compile for armv7:

cd deps
mkdir -p pbc-arm
cd pbc-arm
../protobuf-c/configure --host=arm-linux-gnueabihf --prefix=`pwd`/../arm-linux-gnueabihf --disable-protoc CC=`pwd`/../bin/arm-linux-gnueabihf-gcc
make install
cd ../..
[edit] Cross Compiling for ARMv8

If you would like to cross-compile for armv8:

cd deps
mkdir -p pbc-aarch64
cd pbc-aarch64
 ../protobuf-c/configure --host=aarch64-linux-gnu --prefix=`pwd`/../aarch64-linux-gnu --disable-protoc CC=`pwd`/../bin/aarch64-linux-gnu-gcc
make install
cd ../..

[edit] Building CRIU From Source

[edit] Native Compilation

With the CRIU source obtained in the first step and dependencies satisfied in the second step, we are now compile CRIU. For native compilation with the dependencies met using distribution packages, simply run make in the CRIU source directory.

Here is an example of building natively specifying manually built dependencies.

make \
  USERCFLAGS="-I`pwd`/deps/`uname -m`-linux-gnu/include -L`pwd`/deps/`uname -m`-linux-gnu/lib" \
  PATH="`pwd`/deps/`uname -m`-linux-gnu/bin:$PATH"

[edit] Cross Compilation for ARMv7

make \
  ARCH=arm \
  CROSS_COMPILE=`pwd`/deps/bin/arm-linux-gnueabihf- \
  USERCFLAGS="-I`pwd`/deps/arm-linux-gnueabihf/include -L`pwd`/deps/arm-linux-gnueabihf/lib" \
  PATH="`pwd`/deps/`uname -m`-linux-gnu/bin:$PATH"

[edit] Cross Compilation for ARMv8

 make \
  ARCH=aarch64 \
  CROSS_COMPILE=`pwd`/deps/bin/aarch64-linux-gnu- \
  USERCFLAGS="-I`pwd`/deps/aarch64-linux-gnu/include -L`pwd`/deps/aarch64-linux-gnu/lib" \
  PATH="`pwd`/deps/`uname -m`-linux-gnu/bin:$PATH"

[edit] Linux Kernel

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 must be enabled for CRIU to work:

General setup -> Checkpoint/restore support
General setup -> Namespaces support
General setup -> Namespaces support -> UTS namespace
General setup -> Namespaces support -> IPC namespace
General setup -> Namespaces support -> PID namespaces
General setup -> Namespaces support -> Network namespace
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

For some usage scenarios there is an ability to track memory changes and produce incremental dumps. Need to enable

Processor type and features -> Track memory changes

At the moment it's known that CRIU will NOT work if packet generator module is loaded. Thus make sure that either module is unloaded or not compiled at all.

Networking support -> Networking options -> Network testing -> Packet generator

[edit] iproute2

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 CR_IP_TOOL.

[edit] Checking That 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 tests/zdtm/ directory.

There's a known issue with BTRFS spoiling dev_t values for files and sockets! Not all tests will work on it.

[edit] Using CR tools

Please see Usage and Advanced usage, as well as Category:HOWTO.

Personal tools

Other sites