Difference between revisions of "Main Page"

From CRIU
Jump to navigation Jump to search
(Update coverage link to coveralls.io)
m (rm one mention of "in userspace", there are too many anyway)
Line 1: Line 1:
 
{{Download box|right}}
 
{{Download box|right}}
 
__NOTOC__
 
__NOTOC__
<big>Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux in userspace.
+
<big>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 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.
 
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.

Revision as of 04:13, 1 September 2016

Download
Tarball: criu-3.17.tar.gz
Version: 3.17 "Radiant Redstart"
Released:
GIT tag: v3.17
InstallationUsage
Releases

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


Using

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

CLI, RPC and C API
Three ways to start using the C/R functionality
Usage scenarios
Ideas how criu can be used (some are crazy indeed)
Category:HOWTO
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.
Category:API
Collection of pages about CRIU's API.
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.
Contacts
Ways to communicate with CRIU community

Developing

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

Images
Description of image files format
Plugins
CRIU can call plugins provided by people
Upstream kernel commits
Mainline kernel commits tracker
Recent commits
CRIU tool repository commits
Manpages
Kernel's manpages commits tracker
ZDTM Test Suite
Zero downtime test suite
TODO
Current TODO list
User namespace
Implementing user namespace support
Postulates
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

Events
Feed-icon.svg RSSAtom

stackconf 2022

Stackconf.png

Jul 19, Berlin

Adrian Reber Kubernetes and Checkpoint/Restore```




Under the hood

External links

More external articles...

Audio

Other