Difference between revisions of "ZDTM test suite"

From CRIU
Jump to navigation Jump to search
m
Line 1: Line 1:
−
{| class="wikitable"
+
== Description ==
−
|-
+
 
−
! Name
+
ZDTM stands for zero-down-time-migration. It's test suite developed for testing how OpenVZ live migration works. We use this test suite for checking how crtools do their job. The suit consists of many small atomic tests -- each puts a process into some "state" (opens a file, maps a memory segment, puts data in a pipe, etc.), then asks to be checkpointed and restored. The in checks that the "state" was preserved (file is still open, memory is still mapped, pipe contains what was put into it).
−
! Status
+
 
−
|-
+
== Running ==
−
! colspan="2" | Static
+
 
−
|-
+
You can run the tests manually by issuing a <code>make <testname>.pid</code> command. After you've done c/r-ing it you should run <code>make <testname>.out</code> and check for the <testname>.out file contents.
−
|busyloop00||+
+
 
−
|-
+
If you don't want to mess with this you can use the <code>zdtm.sh</code> script. When launched without arguments runs all the tests one-by-one. The exact test can be specified by the command line argument. The <code>-l</code> option lists the tests it can run.
−
|cwd00||+
 
−
|-
 
−
|deleted_dev||
 
−
|-
 
−
|deleted_unix_sock||
 
−
|-
 
−
|env00||+
 
−
|-
 
−
|fifo||
 
−
|-
 
−
|fifo_wronly||
 
−
|-
 
−
|file_attr||
 
−
|-
 
−
|fpu00||
 
−
|-
 
−
|futex||+
 
−
|-
 
−
|inotify_system||
 
−
|-
 
−
|link10||
 
−
|-
 
−
|maps00||+
 
−
|-
 
−
|mmx00||
 
−
|-
 
−
|mprotect00||+
 
−
|-
 
−
|msgque||+
 
−
|-
 
−
|mtime_mmap||+
 
−
|-
 
−
|overmount_dev||
 
−
|-
 
−
|overmount_fifo||
 
−
|-
 
−
|overmount_file||
 
−
|-
 
−
|overmount_sock||
 
−
|-
 
−
|pid00||FAIL: pid00.c:37: ppid != getppid()
 
−
|-
 
−
|pipe00||+
 
−
|-
 
−
|route_rules||
 
−
|-
 
−
|shm||+
 
−
|-
 
−
|sem||+
 
−
|-
 
−
|sleeping00||+
 
−
|-
 
−
|socket_aio||
 
−
|-
 
−
|sse00||
 
−
|-
 
−
|sse20||
 
−
|-
 
−
|timers||
 
−
|-
 
−
|umask00||
 
−
|-
 
−
|unbound_sock||
 
−
|-
 
−
|unlink_fifo||
 
−
|-
 
−
|unlink_fifo_wronly||
 
−
|-
 
−
|unlink_fstat00||
 
−
|-
 
−
|unlink_fstat01||
 
−
|-
 
−
|unlink_largefile||
 
−
|-
 
−
|wait00||+
 
−
|-
 
−
|write_read00||+
 
−
|-
 
−
|write_read01||+
 
−
|-
 
−
|write_read02||+
 
−
|-
 
−
|write_read10||
 
−
|-
 
−
|zombie00||+
 
−
|-
 
−
|socket_listen||+
 
−
|-
 
−
! colspan="2" | Streaming
 
−
|-
 
−
|fifo_dyn||
 
−
|-
 
−
|fifo_loop||
 
−
|-
 
−
|file_aio||
 
−
|-
 
−
|netlink00||
 
−
|-
 
−
|pipe_loop00||+
 
−
|-
 
−
|pipe_shared00||+
 
−
|-
 
−
|socket_loop00||+
 
−
|-
 
−
|unix_sock||
 
−
|-
 
−
! colspan="2" | Transition
 
−
|-
 
−
|epoll||
 
−
|-
 
−
|file_read||+
 
−
|-
 
−
|ipc||+
 
−
|-
 
−
|ptrace||
 
−
|}
 

Revision as of 10:28, 20 July 2012

Description

ZDTM stands for zero-down-time-migration. It's test suite developed for testing how OpenVZ live migration works. We use this test suite for checking how crtools do their job. The suit consists of many small atomic tests -- each puts a process into some "state" (opens a file, maps a memory segment, puts data in a pipe, etc.), then asks to be checkpointed and restored. The in checks that the "state" was preserved (file is still open, memory is still mapped, pipe contains what was put into it).

Running

You can run the tests manually by issuing a make <testname>.pid command. After you've done c/r-ing it you should run make <testname>.out and check for the <testname>.out file contents.

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

Retrieved from "https://criu.org/index.php?title=ZDTM_test_suite&oldid=303"