Difference between revisions of "Main Page"
(rework attributions) |
(add pronunciation (most people think it's "crai-you")) |
||
| Line 3: | Line 3: | ||
Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux in userspace. | Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux in userspace. | ||
| − | Checkpoint/Restore In Userspace, or CRIU, 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, w: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. |
<div style="background-color: #fafafa; padding: 1em;" class="plainlinks"> | <div style="background-color: #fafafa; padding: 1em;" class="plainlinks"> | ||
Revision as of 17:54, 1 April 2013
|
Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux in userspace.
Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, w: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
- How to run the tool
- Usage scenarios
- Ideas how crtools can be used (some are crazy indeed)
- What software is supported
- Describes TODO list in higher level terms
- LXC
- How to dump and restore an LXC container
- 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.
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 crtools code paths
|
Under the hood
External links
- 2024-11-14, On-demand and Parallel Checkpoint/Restore for GPU Applications
- 2024-09-06, Live Migration of Multi-Container Kubernetes Pods in Multi-Cluster Serverless Edge Systems
- 2024-09-04, Towards Efficient End-to-End Encryption for Container Checkpointing Systems
- 2024-08-04, Custom Page Fault Handling With eBPF
- 2024-08-03, Software-based Live Migration for Containerized RDMA
- 2024-07-30, Packet Buffering to Minimize Service Downtime and Packet Loss During Redundancy Switchover
- 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-07-23, Dapper: A Lightweight and Extensible Framework for Live Program State Rewriting
Other
- Project history
- Logo description
- Events
- Join the CRIU acronym fun