Difference between revisions of "Main Page"
Saied Kazemi (talk | contribs) |
|||
| Line 29: | Line 29: | ||
;[[:Category:HOWTO]] | ;[[: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. | + | : 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]] | ;[[:Category:API]] | ||
Revision as of 19:01, 28 January 2015
|
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
- Getting packages for your distribution
- Or try manual installation 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. 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.
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
- 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
|
External links
- 2025-08-13, Software Availability Protection in Cyber-Physical Systems
- 2025-07-14, PhoenixOS: Concurrent OS-level GPU Checkpoint and Restore with Validated Speculation
- 2025-06-18, Improving Checkpoint/Restore Functionality in Kubernetes
- 2025-06-12, MOSE: A Novel Orchestration Framework for Stateful Microservice Migration at the Edge
- 2025-05-14, Elastic Vertical Memory Management for Container-based Stateful Applications in Kubernetes
- 2025-05-02, Practice and Observation: Live Migration for MPI Workload
- 2025-04-28, GRANNY: Granular Management of Compute-Intensive Applications in the Cloud
- 2025-04-28, KubeSPT: Stateful Pod Teleportation for Service Resilience with Live Migration
- 2025-04-04, Optimizing Stateful Microservice Migration in Kubernetes with MS2M and Forensic Checkpointing
- 2025-03-30, CXLfork: Fast Remote Fork over CXL Fabrics
- 2025-02-23, CRIUgpu: Transparent Checkpointing of GPU-Accelerated Workloads
Other
- Project history
- Logo description
- Events
- Join the CRIU acronym fun