Difference between revisions of "Cpuinfo"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
= CPU capability problem = | = CPU capability problem = | ||
| − | Because CRIU allows to live migrate containers (see [[Live migration | + | Because CRIU allows to live migrate containers (see [[Live_migration | 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. | Thus there should be a way to test if destination machine is capable of running container being migrated. | ||
Revision as of 18:57, 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.
Saving 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.