ZDTM test suite

Revision as of 12:40, 14 September 2018 by Radostin (talk | contribs) (All zdtm tests: Add more detailed description for --lazy-pages, --lazy-migrate and --remote-lazy-pages.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

ZDTM stands for Zero DownTime Migration. ZDTM test suite was developed for testing how OpenVZ live migration works. CRIU also uses this test suite.

The suite consists of many small atomic tests. Each test case creates a process, puts it into some specific state (opens a file, maps a memory segment, puts data in a pipe, etc.), then asks to be checkpointed and restored. Upon restoring, it checks that the state was preserved (file is still opened, memory is still mapped, pipe contains what was put into it, etc).



Install libaio-devel (RPM) or libaio-dev (DEB). For the test launcher zdtm.py you need PyYAML (RPM) or python-yaml (DEB).

There's also a known issue with BTRFS spoiling dev_t values for files and sockets! Not all tests will work on it, so it's better to use other FS.

All zdtm tests[edit]

You can run all the tests by:

      test/zdtm.py run -a

This would run the tests in basic variation -- run the test, checkpoint, restore, check for results.

There are more variations, each is an option to the zdtm.py. Here they are:

Start tests and check results, omitting checkpoint/restore steps. Used to check that the tests themselves are working.
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>
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>
Start the test, then do a <number> of pre-dumps, then checkpoint, restore and check results. Used to check that pre-dumps work.
Run tests, but dumps (and pre-dumps) will go through the page server.
Run tests, but restore in a so-called sibling mode. Used by LXC and Docker.
--snaps (in conjunction with --pre)
Instead of pre-dumps do full dumps.
--user (only works with --norst)
Check how criu works when run from non-root.
Restore tests and join existing namespace.
Restore tests in empty net namespace.
Instead of pre-dumps do full dumps.
Auto-deduplicate images on iterations.
Manual deduplicate images on iterations.
Check that --leave-stopped option stops process tree.
Test fault injection.
Generate CRIU strace-s for sat tool (restore is fake, images are kept).
Do step-by-step execution, asking user for keypress to continue.
Use freeze cgroup (path:state).
Run CRIU via RPC rather than CLI.
Use automatic images transfer.
Run test in parallel.
Don't run tests, just pretend to.
Add script to be notified by CRIU.
Whether or not to keep images after test. Possible values: always, never, failed (default).
Generate summary report in directory.
Keep running tests in spite of failures.
Don't care about a non-zero kernel taint flag.
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.
Allows testing of post-copy migration when running ns or uns 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.
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.
Specify a test suite title.
Show CRIU Statistics.
Path to CRIU binary (default: ../criu/criu).
Path to crit binary (default: ../crit/crit).


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 but the user one, criu c/r-s test with all the namespaces. The uns is user namespace, it's like ns but with user namespace in the game.

By default tests are run on all flavors they can, but one can chose flavor with -f flavor option.

Specific tests[edit]

You can run a single test with

      zdtm.py run -t test-name

The simplest test is zdtm/static/env00. It has the bare minimal a process might have -- a little bit of memory, a signal handler and one opened file. If CRIU cannot C/R this test, it surely cannot do anything else.

You can also run only the test proggies themselves manually by issuing the

      make test-name.pid

command. After you've done c/r-ing it you should run

      make test-name.out

and check for the test-name.out file contents.

If you don't want to mess with this, you can use the zdtm.py run script. When launched with the -a option, it runs all the tests one-by-one. The exact test can be specified by a command line argument. The list command lists the tests it can run.

See also[edit]