[CRIU] can criu restore data after the reboot or using kexec ?

[Pavel Emelyanov]

On 09/02/2015 01:51 PM, lei yang wrote:
> Hi experts,
> 
> My target is using the nfs as root
> root at ISG_WalnutCanyonII-2:~# cat /proc/cmdline
> console=ttyS0,115200 root=/dev/nfs rw nfsroot=128.224.165.20:/export/pxeboot/vlm-boards/22574/rootfs rw ip=dhcp intel_iommu=off no_console_suspend=1 crashkernel=512M at 64M
> 
> I follow below step:
> ./test.sh  < /dev/null &> test.log &
>  criu dump -v4 -o dump.log -D checkpoint/ -t 1264 --shell-job
> then reboot
> criu restore -d -D checkpoint/ -vvvv -o restore.log

Try to use the --shell-job for restore too.

> it doesn't restore the test.sh, any help?
> 
> if I use kexec, any point need to be careful ?

For kexec case we have the WIP called RKU (rebootless kernel update) or KUP
(kernel updater). Here's my talk at Plumbers last year [1], and And there 
also was an article from Sanidhya at [2], but it has moved :) so I'm putting
the author in Cc.
  
[1] http://www.slideshare.net/openvz/rku-dusseldorf 
[2] https://sslab.gtisc.gatech.edu/2015/rebootless-kernel-update.html

-- Pavel