Difference between revisions of "Main Page"
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
|
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
- 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
|
Under the hood
External links
- 2024-09-04, Towards Efficient End-to-End Encryption for Container Checkpointing Systems
- 2024-08-03, Software-based Live Migration for Containerized RDMA
- 2024-07-30, Don't, Stop, Drop, Pause: Forensics of CONtainer CheckPOINTs (ConPoint)
- 2024-07-25, MDB-KCP: persistence framework of in-memory database with CRIU-based container checkpoint in Kubernetes
- 2024-04-22, Just-In-Time Checkpointing: Low Cost Error Recovery from Deep Learning Training Failures
- 2024-04-22, Pronghorn: Effective Checkpoint Orchestration for Serverless Hot-Starts
- 2024-01-29, Prebaking runtime environments to improve the FaaS cold start latency
- 2023-11-12, Checkpoint/Restart for CUDA Kernels
- 2023-10-23, Evicting for the greater good: The Case for Reactive Checkpointing in Serverless Computing
Other
- Project history
- Logo description
- Events
- Join the CRIU acronym fun