Difference between revisions of "Main Page"

Jump to: navigation, search
(crtools -> criu)
Line 21: Line 21:
;[[Usage scenarios]]
;[[Usage scenarios]]
: Ideas how crtools can be used (some are crazy indeed)
: Ideas how criu can be used (some are crazy indeed)
;[[What software is supported]]
;[[What software is supported]]
Line 57: Line 57:
;[http://criu.org/cov/ Code coverage results]
;[http://criu.org/cov/ Code coverage results]
: Shows how zdtm run covers the crtools code paths
: Shows how zdtm run covers the criu code paths
;[[How to submit patches]]
;[[How to submit patches]]
Line 75: Line 75:
* [[Checkpoint/Restore]]
* [[Checkpoint/Restore]]
* [[TCP connection]]
* [[TCP connection]]
* [[Porting crtools to new kernel releases]]
* [[Porting criu to new kernel releases]]
* [[Files]]
* [[Files]]
* [[Pending signals]]
* [[Pending signals]]

Revision as of 16:32, 30 April 2013

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 in userspace.

Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a software tool for Linux operating system. Using this tool, you can freeze a running application (or part of it) and checkpoint it to a hard drive as a collection of files. You can then use the files to restore and run the application from the point it was frozen at. The distinctive feature of the CRIU project is that it is mainly implemented in user space.


What to do to have CRIU on your system
How to run the tool
Usage scenarios
Ideas how criu can be used (some are crazy indeed)
What software is supported
Describes TODO list in higher level terms
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.
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.


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

Description of image files format
Mainline kernel commits tracker
Kernel's manpages commits tracker
ZDTM Test Suite
Zero downtime test suite
Current TODO list
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

Feed-icon.svg RSSAtom



Feburary 1, 2020, Brussels, Belgium

Container Live Migration

--User:Rppt 19:22, 28 February 2020‎ (UTC)

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)

Under the hood

External links

More external articles...