Difference between revisions of "Installation"

From CRIU
Jump to: navigation, search
(Tools installation: there are no other branches)
(Kernel configuration)
Line 32: Line 32:
 
* Networking support -> Networking options -> TCP/IP networking -> INET: socket monitoring interface -> UDP: socket monitoring interface (<code>CONFIG_INET_UDP_DIAG</code>)
 
* Networking support -> Networking options -> TCP/IP networking -> INET: socket monitoring interface -> UDP: socket monitoring interface (<code>CONFIG_INET_UDP_DIAG</code>)
 
* Networking support -> Networking options -> Packet socket -> Packet: sockets monitoring interface (<code>CONFIG_PACKET_DIAG</code>)
 
* Networking support -> Networking options -> Packet socket -> Packet: sockets monitoring interface (<code>CONFIG_PACKET_DIAG</code>)
 +
* Networking support -> Networking options -> Netlink socket -> Netlink: sockets monitoring interface (<code>CONFIG_NETLINK_DIAG</code>)
  
 
Note you might have to enable
 
Note you might have to enable

Revision as of 08:38, 23 May 2013

criu is an utility to checkpoint/restore a process tree.

Tools installation

Get the latest release:

Tarball: criu-3.13.tar.bz2
Version: 3.13 "Silicon Willet"
Released: 11 Sep 2019
GIT tag: v3.13

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 rpm-based world this is protobuf-c-devel package. 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/.

Then run make in the sources root.

Kernel configuration

The v3.9 upstream kernel already has most of the required functionality merged. Some is still out-of-tree though, so you might need to clone the linux-cr.git, checkout the latest branch and compile the kernel.

Make sure you have the following options turned on:

  • General setup -> Checkpoint/restore support (CONFIG_CHECKPOINT_RESTORE)
  • General setup -> open by fhandle syscalls (CONFIG_FHANDLE)
  • General setup -> Enable eventfd() system call (CONFIG_EVENTFD)
  • General setup -> Enable eventpoll support (CONFIG_EPOLL)
  • File systems -> Inotify support for userspace (CONFIG_INOTIFY_USER)
  • Executable file formats -> Emulations -> IA32 Emulation (CONFIG_IA32_EMULATION)
  • Networking support -> Networking options -> Unix domain sockets -> UNIX: socket monitoring interface (CONFIG_UNIX_DIAG)
  • Networking support -> Networking options -> TCP/IP networking -> INET: socket monitoring interface (CONFIG_INET_DIAG)
  • Networking support -> Networking options -> TCP/IP networking -> INET: socket monitoring interface -> UDP: socket monitoring interface (CONFIG_INET_UDP_DIAG)
  • Networking support -> Networking options -> Packet socket -> Packet: sockets monitoring interface (CONFIG_PACKET_DIAG)
  • Networking support -> Networking options -> Netlink socket -> Netlink: sockets monitoring interface (CONFIG_NETLINK_DIAG)

Note you might have to enable

  • General setup -> Configure standard kernel features (expert users) (CONFIG_EXPERT)

option, which depends on

  • General setup -> Embedded system (CONFIG_EMBEDDED)

(welcome to Kconfig reverse chains hell).

iproute2

A modified version of iproute2 is needed for dumping network namespaces. The good one can be cloned from iproute2. It should be compiled and a path to ip is written in the environment variable CR_IP_TOOL.

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 tests/zdtm/ directory.

Using CR tools

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