Difference between revisions of "Main Page"

Jump to: navigation, search
m (Grammar)
(Fix the coerall.io link)
Line 76: Line 76:
: What to keep in mind when writing new code
: What to keep in mind when writing new code
;[https://coveralls.io/github/xemul/criu Code coverage results]
;[https://coveralls.io/github/checkpoint-restore/criu Code coverage results]
: Shows how zdtm run covers the criu code paths
: Shows how zdtm run covers the criu code paths

Revision as of 19:19, 27 November 2017

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

Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux.

Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a software tool for the Linux operating system. Using this tool, you can freeze a running application (or part of it) and checkpoint it as a collection of files on disk. You can then use the files to restore the application and run it exactly as it was during the time of the freeze. With this feature, application live migration, snapshots, remote debugging, and many other things are possible.

CRIU started as a project of Virtuozzo and grew with tremendous help from the community. It is currently used by (integrated into) OpenVZ, LXC/LXD, Docker, and other software, and CRIU packages is included into many Linux distributions.

Feed-icon.svg RSSAtom

Linux Plumbers Conference 2019


September 9-11, Lisbon, Portugal

Update on Task Migration at Google Using CRIU

CRIU and the PID dance

CRIU: Reworking vDSO proxification, syscall restart

Secure Image-less Container Migration

--User:Avagin 14:05, 23 Aug 2019 (UTC)

Google Summer of Code 2019


Mar-Sep 2019

Google Summer of Code

--User:Avagin 21:32, 26 Feb 2019 (PST)


Getting packages for your distribution
Or try manual installation to have CRIU on your system

Three ways to start using the C/R functionality. More info about APIs.
Usage scenarios
Ideas how criu can be used (some are crazy indeed)
Collection of real world examples of how to use CRIU. Some are complex, some are not. HOW TO dump a simple loop might be the best one to start with. Also a set of asciinema records for real-life examples.
FAQ & When C/R fails
A sort of troubleshooting guide
What can change after C/R
CRIU cannot (yet) save and restore every single bit of tasks' state. This page describes what bits visible through standard kernel API are such.
What cannot be checkpointed
What an application could do to make CRIU refuse to dump it.
Ways to communicate with CRIU community


If you're interested in CRIU development, please subscribe to the criu mailing list: https://lists.openvz.org/mailman/listinfo/criu

Description of image files format
CRIU can call plugins provided by people
Upstream kernel commits
Mainline kernel commits tracker
Recent commits
CRIU tool repository commits
Kernel's manpages commits tracker
ZDTM Test Suite
Zero downtime test suite
Current TODO list
User namespace
Implementing user namespace support
What to keep in mind when writing new code
Code coverage results
Shows how zdtm run covers the criu code paths
How to submit patches