Difference between revisions of "Installation"

From CRIU
Jump to: navigation, search
m (moved CR tools to Installation)
(misc edits)
Line 1: Line 1:
== What CRtools is ==
+
'''CRtools''' is an utility to checkpoint/restore a process tree.
  
'''CRtools''' is an utility to checkpoint/restore process tree. Unlike checkpoint/restore implemented completely in kernel space,
+
== Tools installation ==
it tries to achieve the same target operating in user space. Since the tools and overall concept are still under heavy development
 
stage there are some known limitations applied, in particular only pure x86-64 environment is supported, no IA32 emulation allowed.
 
  
== Download and build crtools ==
+
Get the latest release from [[Releases]].
  
The '''crtools''' utility itself is hosted at [http://git.criu.org/?p=crtools.git;a=summary git.criu.org].
+
Alternatively, use [http://git.criu.org/?p=crtools.git;a=summary git.criu.org] git repository.
 
Clone this repo to test new functionality. Anything but '''master''' branch are development ones, don't refer on them.
 
Clone this repo to test new functionality. Anything but '''master''' branch are development ones, don't refer on them.
  
Before building also install the C bindings for Google's Protocol Buffers. In rpm-based distros this is <code>protobuf-c</code> package.
+
Before building, make sure you have C bindings for Google's Protocol Buffers installed. In rpm-based world this is <code>protobuf-c-devel</code> package.
  
The run <code>make</code> in the sources root.
+
Then run <code>make</code> in the sources root.
  
== Configure the linux kernel ==
+
== Kernel configuration ==
  
Make sure you have the following options turned on
+
Make sure you have the following options turned on:
  
 
* General setup -> Checkpoint/restore support (<code>CONFIG_CHECKPOINT_RESTORE</code>)
 
* General setup -> Checkpoint/restore support (<code>CONFIG_CHECKPOINT_RESTORE</code>)

Revision as of 11:22, 23 July 2012

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

Tools installation

Get the latest release from Releases.

Alternatively, use git.criu.org git repository. Clone this repo to test new functionality. Anything but master branch are development ones, don't refer on them.

Before building, make sure you have C bindings for Google's Protocol Buffers installed. In rpm-based world this is protobuf-c-devel package.

Then run make in the sources root.

Kernel configuration

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)
  • 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)

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

The v3.5 upstream kernel already has most of the required functionality merged. Some is sill out-of-tree though, so you might need to clone the linux-2.6-crtools.git, checkout the crtools-3.5 branch and compile the kernel.

Checking how it works

You can first look into the ZDTM Test Suite which sits in the tests/zdtm/ directory.

Using CR tools

Please see running CR tools article.

CR tools mailing list

If you're interested in CR tools development don't hesitate to subscribe to the CRtools mailing list which can be found here [1].