Difference between revisions of "Installation"
(crtools -> criu) |
(Mention crtools check) |
||
| Line 48: | Line 48: | ||
== Checking how it works == | == Checking how it works == | ||
| + | |||
| + | First thing to do is to run | ||
| + | |||
| + | <pre> | ||
| + | # crtools check --ms | ||
| + | </pre> | ||
| + | |||
| + | 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 <code>--ms</code> option should not be used, in this case CRIU would | ||
| + | check for ''all'' the kernel features to work. | ||
You can first look into the [[ZDTM Test Suite]] which sits in the <code>tests/zdtm/</code> directory. | You can first look into the [[ZDTM Test Suite]] which sits in the <code>tests/zdtm/</code> directory. | ||
Revision as of 10:08, 4 May 2013
criu is an utility to checkpoint/restore a process tree.
Tools installation
Get the latest release:
| Tarball: | criu-4.0.tar.gz |
| Version: | 4.0 "CRIUDA" |
| Released: | 20 Sep 2024 |
| GIT tag: | v4.0 |
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.
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.5 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 crtools-v3.9-rc1 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)
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
# crtools 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 first look into 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.