Difference between revisions of "Main Page"
Jump to navigation
Jump to search
(new layout with EVENTS) |
(rm end crap) |
||
| Line 67: | Line 67: | ||
* [[Events]] | * [[Events]] | ||
</div> | </div> | ||
| − | |||
| − | |||
| − | |||
Revision as of 14:10, 3 October 2012
| CRIU is a sub-project of http://static.openvz.org/wiki/openvz-logo.png |
Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux in userspace.
|
Using
- CR tools
- Main checkpoint/restore utility description (sort of HOWTO)
- 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
Developing
If you're interested in CRIU development, subscribe to the criu mailing list: https://openvz.org/mailman/listinfo/criu
- Images
- Description of image files format
- Commits
- Mainline kernel commits tracker
- ZDTM Test Suite
- Zero downtime test suite
- TODO
- Current TODO list
|
Under the hood
External links
- 2026-02-24, GPU Checkpoint/Restore Made Fast and Lightweight
- 2026-01-21, Announcing the Checkpoint/Restore Working Group
- 2025-11-17, Engine-Agnostic Model Hot-Swapping for Cost-Effective LLM Inference
- 2025-09-16, Checkpointing and State Transfer for Industrial Controller Redundancy
- 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-17, LWN.net: A parallel path for GPU restore in CRIU
- 2025-06-13, Kubernetes Scheduling with Checkpoint/Restore: Challenges and Open Problems