Difference between revisions of "Main Page"

From CRIU
Jump to navigation Jump to search
Line 31: Line 31:
 
;[[What can change after C/R]]
 
;[[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.
 
: 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]]
 +
: This article describes what application can do to make CRIU refuse to dump it. It can be used as some sort of troubleshooting guide.
  
 
</div>
 
</div>

Revision as of 19:06, 26 November 2013

Download
Tarball: criu-4.0.tar.gz
Version: 4.0 "CRIUDA"
Released: 20 Sep 2024
GIT tag: v4.0
InstallationUsage
Releases

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.


Using

Installation
What to do to have CRIU on your system
CLI and RPC
Two ways to start using the C/R functionality
Usage scenarios
Ideas how criu can be used (some are crazy indeed)
What software is supported
Describes TODO list in higher level terms
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.
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
This article describes what application can do to make CRIU refuse to dump it. It can be used as some sort of troubleshooting guide.

Developing

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

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


LinuxDays 2024

Linux-days-cz.svg

13 Oct 2024, On the Edge of Tomorrow: Checkpoint/Restore in Containers


Kubernetes Community Days Austria

Kcd-austria.svg

09 Oct 2024, Forensic container checkpointing and analysis


Linux Plumbers Conference 2024

Linuxplumbers.png

18-20 Sep 2024, Containers and Checkpoint/Restore Microconference

Other talks:
* Userspace memory persistence over kexec
* Checkpoint/Restore In eBPF (CRIB)




Under the hood

External links

More external articles...

Other