Difference between revisions of "Cpuinfo"

From CRIU
Jump to: navigation, search
(Created page with "= CPU capability problem = Because CRIU allows to live migrate containers (see Live_migration for details) it might happen that CPU a container has been ...")
 
Line 4: Line 4:
  
 
Thus there should be a way to test if destination machine is capable of running container being migrated.
 
Thus there should be a way to test if destination machine is capable of running container being migrated.
 +
 +
== Save CPU capabilities into an image file ==
 +
 +
CRIU does not write CPU capabilities into an image by default in a sake of speed. Instead one have to run CRIU as
 +
 +
  criu cpuinfo dump
 +
 +
to produce ''cpuinfo'' image file which consists of bits representing the capabilities current CPU support.

Revision as of 18:04, 11 November 2014

CPU capability problem

Because CRIU allows to live migrate containers (see Live_migration for details) it might happen that CPU a container has been ran on differ from the target CPU. For typical programs this might be not a problem but if a program get compiled with optimization which use a particular CPU feature (say AVX instruction and etc) the lack of the feature on a destination machine will lead to execution exception in a best case.

Thus there should be a way to test if destination machine is capable of running container being migrated.

Save CPU capabilities into an image file

CRIU does not write CPU capabilities into an image by default in a sake of speed. Instead one have to run CRIU as

 criu cpuinfo dump

to produce cpuinfo image file which consists of bits representing the capabilities current CPU support.