[CRIU] Using p.haul migration failure

Pavel Emelyanov xemul at parallels.com
Wed Nov 5 05:38:45 PST 2014


On 11/05/2014 06:34 PM, Sowmini Varadhan wrote:
> On (11/05/14 15:10), Pavel Emelyanov wrote:
>>> Examining the log file, seems like the issue is this
>>>
>>>     (00.054526) Error (files-reg.c:792): Unable to look up the 18 mount
>>>     (00.054542) BUF 0x7f3998ccc000 >
>>>     (00.054549) ----------------------------------------
>>>     (00.054552) Error (cr-dump.c:1596): Dump files (pid: 2681) failed with -1
>>
>> There are problems with mount points. Can you do "criu dump -R" on
>> your container
>> successfully?
>>
> 
> Assuming that you want me to use the pid of the init for the container, 
> here's what I get (similar to above):
> 
> [root at sowmini-vm p.haul]# criu dump -t 2681 -R
> Error (mount.c:453): 84:./lib64 doesn't have a proper root mount
> Error (files-reg.c:792): Unable to look up the 18 mount
> Error (cr-dump.c:1596): Dump files (pid: 2681) failed with -1
> Error (cr-dump.c:1952): Dumping FAILED.
> 
> Is the "./lib64" relative to container rootfs?

Yes. Presumably the lib64 is bind-mounted from the host on
container start. CRIU can handle such things, but not yet the
p.haul can.

Thanks,
Pavel



More information about the CRIU mailing list