Difference between revisions of "CRIT"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
Right now we store the images version in inventory.img and collect info about [[what's bad with V1 images]]. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images. | Right now we store the images version in inventory.img and collect info about [[what's bad with V1 images]]. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images. | ||
| + | |||
| + | === Show images statistics === | ||
| + | |||
| + | E.g. -- total number of processes, files, memory, sockets, etc. | ||
Revision as of 13:53, 7 November 2014
This page describes the CRiu Image Tool.
Functionality
Convert images to human-readable and back
This is the replacement for (rather nasty) criu show code. Also this is the way to edit the images before restoring from them.
Convert to json (and back)
Same as before, but the human-readable format is JSON
Generate core files out of task images
All the needed information is in core-$pid.img and pagemap-$pid.img
On-the-fly conversion
There's an idea to make CRIU spawn CRIT and read images "through" it, to allow for at-the-restore-time modifications
Convert between different image versions
Right now we store the images version in inventory.img and collect info about what's bad with V1 images. If some day we have v2, CRIT will convert from v1. And for backward compatibility we'll use on-the-fly conversion when restoring from old images.
Show images statistics
E.g. -- total number of processes, files, memory, sockets, etc.