Changes

Jump to navigation Jump to search
89 bytes removed ,  13:34, 12 July 2017
no edit summary
Line 45: Line 45:  
For APT use the <code>--no-install-recommends</code> parameter is to avoid asciidoc pulling in a lot of dependencies.
 
For APT use the <code>--no-install-recommends</code> parameter is to avoid asciidoc pulling in a lot of dependencies.
 
Also read about [[ZDTM test suite]] if you will run CRIU tests, those sources need other deps.
 
Also read about [[ZDTM test suite]] if you will run CRIU tests, those sources need other deps.
  −
== Ensuring the Linux Kernel is up-to-date ==
  −
  −
Linux kernel v3.11 or newer is required, with some specific config options turned on. Various advanced CRIU features might require even newer kernel. If your distribution does not provide needed kernel, you might want to [[Linux kernel|compile one yourself]]. Criu can [[check the kernel]] features presence.
      
== Building the tool ==
 
== Building the tool ==
Line 64: Line 60:  
== Checking That It Works ==
 
== Checking That It Works ==
   −
First thing to do is to [[Checking the kernel|check the kernel]] by running <code>criu check</code>. At the end it should say "Looks OK", if it doesn't the messages on the screen explain what functionality is missing.
+
Linux kernel v3.11 or newer is required, with some specific config options turned on. Various advanced CRIU features might require even newer kernel.  So the first thing to do is to [[Checking the kernel|check the kernel]] by running <code>criu check</code>. At the end it should say "Looks OK", if it doesn't the messages on the screen explain what functionality is missing. If your distribution does not provide needed kernel, you might want to [[Linux kernel|compile one yourself]].
    
You can then try running the [[ZDTM Test Suite]] which sits in the <code>tests/zdtm/</code> directory.
 
You can then try running the [[ZDTM Test Suite]] which sits in the <code>tests/zdtm/</code> directory.

Navigation menu