Line 21: |
Line 21: |
| | | |
| ;--nocr | | ;--nocr |
− | : start tests and check results, omitting checkpoint/restore steps. Used to check that the tests themselves are working. | + | : Start tests and check results, omitting checkpoint/restore steps. Used to check that the tests themselves are working. |
| | | |
| ;--norst | | ;--norst |
− | : start the test, then checkpoint it leaving the tests running, then check the results. Used to check that checkpoint itself is not destructive. | + | : Start the test, then checkpoint it leaving the tests running, then check the results. Used to check that checkpoint itself is not destructive. |
| | | |
| ;--iter <number> | | ;--iter <number> |
− | : start the test, then checkpoint and restore it the <number> of times. Used to check that after restore tests are in checkpoint-able state. | + | : Start the test, then checkpoint and restore it the <number> of times. Used to check that after restore tests are in checkpoint-able state. |
| | | |
| ;--pre <number> | | ;--pre <number> |
− | : start the test, then do a <number> of pre-dumps, then checkpoint, restore and check results. Used to check that pre-dumps work. | + | : Start the test, then do a <number> of pre-dumps, then checkpoint, restore and check results. Used to check that pre-dumps work. |
| | | |
| ;--page-server | | ;--page-server |
− | : run tests, but dumps (and pre-dumps) will go through the [[page server]]. | + | : Run tests, but dumps (and pre-dumps) will go through the [[page server]]. |
| | | |
| ;--sibling | | ;--sibling |
− | : run tests, but restore in a so-called ''sibling'' mode. Used by LXC and Docker. | + | : Run tests, but restore in a so-called ''sibling'' mode. Used by LXC and Docker. |
| | | |
| ;--snaps (in conjunction with --pre) | | ;--snaps (in conjunction with --pre) |
− | : instead of pre-dumps do full dumps | + | : Instead of pre-dumps do full dumps. |
| | | |
| ;--user (only works with --norst) | | ;--user (only works with --norst) |
− | : check how criu works when run from non-root. | + | : Check how criu works when run from non-root. |
| + | |
| + | ;--join-ns |
| + | : Restore tests and join existing namespace. |
| + | |
| + | ;--empty-ns |
| + | : Restore tests in empty net namespace. |
| + | |
| + | ;--snaps |
| + | : Instead of pre-dumps do full dumps. |
| + | |
| + | ;--dedup |
| + | : Auto-deduplicate images on iterations. |
| + | |
| + | ;--noauto-dedup |
| + | : Manual deduplicate images on iterations. |
| + | |
| + | ;--stop |
| + | : Check that --leave-stopped option stops process tree. |
| + | |
| + | ;--fault |
| + | : Test fault injection. |
| + | |
| + | ;--sat |
| + | : Generate CRIU strace-s for sat tool (restore is fake, images are kept). |
| + | |
| + | ;--sbs |
| + | : Do step-by-step execution, asking user for keypress to continue. |
| + | |
| + | ;--freezecg |
| + | : Use freeze cgroup (path:state). |
| + | |
| + | ;--rpc |
| + | : Run CRIU via RPC rather than CLI. |
| + | |
| + | ;--remote |
| + | : Use [[Image_cache/proxy_TODO|automatic images transfer]]. |
| + | |
| + | ;--parallel |
| + | : Run test in parallel. |
| + | |
| + | ;--dry-run |
| + | : Don't run tests, just pretend to. |
| + | |
| + | ;--script |
| + | : Add script to be notified by CRIU. |
| + | |
| + | ;--keep-img |
| + | : Whether or not to keep images after test. Possible values: <code>always</code>, <code>never</code>, <code>failed</code> (default). |
| + | |
| + | ;--report |
| + | : Generate summary report in directory. |
| + | |
| + | ;--keep-going |
| + | : Keep running tests in spite of failures. |
| + | |
| + | ;--ignore-taint |
| + | : Don't care about a non-zero kernel taint flag. |
| + | |
| + | ;--lazy-pages |
| + | : Restore pages on demand. In this case dump works "normally", restore skips the memory pages that can be handled on demand and lazy-pages daemon handles the page faults and reads the memory contents from the image files. |
| + | |
| + | ;--lazy-migrate |
| + | : Allows testing of post-copy migration when running <code>ns</code> or <code>uns</code> flavor. It cannot run with the host flavor because during post-copy migration the migrated tasks should exist both on the source and the destination. |
| + | |
| + | ;--remote-lazy-pages |
| + | : Simulates post-copy memory migration. Here again, the dump works "normally", but the lazy-pages daemon does not read data from the image files but requests it "over the network" for the page-server. It is the page-server that reads memory pages from the images and simulates what 'dump --lazy-pages' wound have done. |
| + | |
| + | ;--title |
| + | : Specify a test suite title. |
| + | |
| + | ;--show-stats |
| + | : Show CRIU [[Statistics]]. |
| + | |
| + | ;--criu-bin |
| + | : Path to CRIU binary (default: <code>../criu/criu</code>). |
| + | |
| + | ;--crit-bin |
| + | : Path to crit binary (default: <code>../crit/crit</code>). |
| | | |
| === Flavors === | | === Flavors === |
| | | |
− | Each test can be executed in up to 3 flavors: h, ns and uns. The first is host flavor, the test is run on host and criu c/r-s it. Ns is namespace flavor, tests are run in all namespaces bu user one, criu c/r-s test with all the namespaces. The uns is usernamespace, it's like ns but with user namespace in the game. | + | Each test can be executed in up to 3 flavors: <code>h</code>, <code>ns</code> and <code>uns</code>. The first is ''host'' flavor, the test is run on host and criu c/r-s it. <code>ns</code> is ''namespace'' flavor, tests are run in all namespaces but the user one, criu c/r-s test with all the namespaces. The <code>uns</code> is ''user namespace'', it's like <code>ns</code> but with user namespace in the game. |
| | | |
| By default tests are run on all flavors they can, but one can chose flavor with <code>-f ''flavor''</code> option. | | By default tests are run on all flavors they can, but one can chose flavor with <code>-f ''flavor''</code> option. |