2,257
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − + − + − to/from json+ + + + + + − -i IN, --in IN input file (stdin by default) − -o OUT, --out OUT output file (stdout by default) − --pretty multi-line with indentation and some fields printed in more human-readable format + + + + + + + + + + + + + + + + + + + + + Line 23:
Line 46: − {{Status|ready}} − + Line 31:
Line 53: − With "--format raw":+ − + Line 56:
Line 78: − + Line 188:
Line 210: − 1953064751, − 1769104175, − 1702113141, − 1664054387, + + + + + − 4294901760, + − 255, Line 216:
Line 238: − 21771440, + + + + + + + + − 21771552, Line 224:
Line 252: − 4278190080, − 4294967295, − 4294967040, − 4294967295, Line 233:
Line 257: − 4278190080, − 4294967040, − 4294967295, + Line 258:
Line 280: − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + − + Line 310:
Line 332: − + Line 339:
Line 361: − + − + Line 359:
Line 381: − + − + Line 394:
Line 416: − {{Status|not ready}}+ − All the needed information is in core-$pid.img and pagemap-$pid.img+ − === On-the-fly conversion ===+ + + + + − {{Status|not ready}}+ + + − 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 ===+ + − {{Status|not ready}}+ − 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 ===+ − {{Status|not ready}}+ − E.g. -- total number of processes, files, memory, sockets, etc.+ − − {{Status|not ready}} + + + + + +
→Planned functionality
== Usage ==
== Usage ==
<pre>
<pre>
usage: crit [-h] [-i IN] [-o OUT] [-f {raw,nice}] {decode,encode}
usage: crit [-h] {decode,encode,info,x,show} ...
CRiu Image Tool
CRiu Image Tool
positional arguments:
positional arguments:
{decode,encode} decode/encode - convert criu image from/to binary type
{decode,encode,info,x,show}
Use crit CMD --help for command-specific help
decode convert criu image from binary type to json
encode convert criu image from json type to binary
info show info about image
x explore image dir
show convert criu image from binary to human-readable json
optional arguments:
optional arguments:
-h, --help show this help message and exit
-h, --help show this help message and exit
</pre>
</pre>
=== Pretty output ===
Command <decode> prints JSON text in one line. This can be read by any further JSON-aware tool for parsing. For human eyes it's more convenient to read JSON multi-line with indentation. CRIT can do this when using the <code>show</code> action or the <code>--pretty</code> option.
Wend doing pretty optput CRIT does a little bit more, than just multiline indented JSON.
; Addresses and registers
: VM addresses and core.img register values are all printed in hex. Since JSON doesn't support this form of numbers, such fields are encoded as strings.
; Bit-fields
: Such things as flags and masks (e.g. sig-block mask) are also better understood when written in hex, so CRIT does this.
; IP addresses
: By default those a printed in decimal, but the "1.2.3.4" for v4 or "::1" for v6 can be seen in the --pretty mode.
; Symbolic names for flags
: Some known bit sets (e.g. MAP_PRIVATE, MAP_ANONYMOUS, etc. for vma->flags) are shown with names.
; Device numbers
: If the field is known to be of <code>dev_t</code> type, it's printed in the <code>major:minor</code> manner
== Functionality ==
== Functionality ==
=== Convert images to JSON and back ===
=== Convert images to JSON 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.
This is the replacement for (rather nasty) <code>criu show</code> code. Also this is the way to edit the images before restoring from them.
It uses [https://developers.google.com/protocol-buffers/docs/reference/python/google.protobuf.text_format-module text_format] as a human-readable format for protobuf messages.
It uses [https://developers.google.com/protocol-buffers/docs/reference/python/google.protobuf.text_format-module text_format] as a human-readable format for protobuf messages.
The output file is structured in the following way.
The output file is structured in the following way.
Without "--pretty":
<pre>
<pre>
{ "magic" : "FOO", "entries" : [{"foo": "bar", "bar": "foo", "extra": "abc"}, {"foo": "bar", "bar" : "foo", "extra" : "abc"} ]}
{ "magic" : "FOO", "entries" : [{"foo": "bar", "bar": "foo", "extra": "abc"}, {"foo": "bar", "bar" : "foo", "extra" : "abc"} ]}
</pre>
</pre>
With "--format nice"(default for stdout):
With "--pretty":
<pre>
<pre>
{
{
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
<b>Example("crit decode -i core-20700.img")</b>
<b>Example("crit decode -i core-5679.img --pretty")</b>
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">
<pre>
<pre>
},
},
"xmm_space": [
"xmm_space": [
0,
0,
4278190080,
4294967295,
4294967295,
1701145715,
3219568,
0,
0,
0,
0,
0,
0,
0,
0,
33,
0,
0,
792358505,
792358505,
65,
65,
0,
0,
37049520,
0,
37049632,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
4294901760,
0,
0,
0,
0,
"clear_tid_addr": 0,
"clear_tid_addr": 0,
"gpregs": {
"gpregs": {
"gs": 0,
"gs": "0x0",
"ip": 140137968588056,
"ip": "0x7f172cf1ea04",
"cx": 18446744073709551615,
"cx": "0xffffffffffffffff",
"cs": 51,
"cs": "0x33",
"ax": 61,
"ax": "0x38",
"orig_ax": 61,
"orig_ax": "0x38",
"di": 18446744073709551615,
"di": "0x1200011",
"es": 0,
"es": "0x0",
"gs_base": 0,
"gs_base": "0x0",
"r14": 0,
"r14": "0x0",
"r15": 4294967295,
"r15": "0x2355e00",
"r12": 21789168,
"r12": "0x7ffffdbf74f0",
"r13": 0,
"r13": "0x0",
"r10": 0,
"r10": "0x7f172d83d9d0",
"r11": 582,
"r11": "0x246",
"fs_base": 140137978173184,
"fs_base": "0x7f172d83d700",
"bp": 2560,
"bp": "0x7ffffdbf7530",
"dx": 0,
"dx": "0x0",
"bx": 0,
"bx": "0x0",
"ds": 0,
"ds": "0x0",
"ss": 43,
"ss": "0x2b",
"sp": 140736135950616,
"sp": "0x7ffffdbf74f0",
"r8": 21789168,
"r8": "0x0",
"r9": 0,
"r9": "0x0",
"fs": 0,
"fs": "0x0",
"si": 140736135950656,
"si": "0x0",
"flags": 582
"flags": "0x246"
}
}
},
},
"cg_set": 1,
"cg_set": 1,
"signals_s": {},
"signals_s": {},
"blk_sigset": 65536,
"blk_sigset": "0x10002",
"exit_code": 0,
"exit_code": 0,
"rlimits": {
"rlimits": {
},
},
{
{
"max": 62845,
"max": 62844,
"cur": 62845
"cur": 62844
},
},
{
{
},
},
{
{
"max": 62845,
"max": 62844,
"cur": 62845
"cur": 62844
},
},
{
{
=== Generate core files out of task images ===
=== Generate core files out of task images ===
Moved into separate project called [[criu-coredump]].
=== Show images statistics ===
E.g. -- total number of processes, files, memory, sockets, etc.
Use
<pre>
crit x $directory_with_images <explore type>
</pre>
Supported explorers are
;'ps'
:to show process tree
;'fds'
:to show files used by tasks
;'mems'
:to show memory mappings info
== Planned functionality ==
=== 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. For details, see https://github.com/xemul/criu/issues/59.
=== 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.
=== Check/validate images ===
=== Check/validate images ===
Check that
Check that
* all images are present
* all images are present
* the inter-images IDs are in consistent state
* the inter-images IDs are in consistent state
For details, see https://github.com/xemul/criu/issues/44.
=== [[Anonymize image files]] ===
Since images contain raw memory dumps people may refuse to send us images for debugging. Need to anonymize them, i.e. -- remove this sensitive information.
[[Category:Images]]
[[Category:Images]]
[[Category:API]]
[[Category:API]]