[CRIU] Error in dump parent process, with child process in different namespace

Hui Kang hkang.sunysb at gmail.com
Thu Jul 30 09:24:31 PDT 2015


Hi, Pavel,
Thanks for you reply. The main purpose is to checkpoint the child process.
I found this in the criu manual

       -n, --namespaces <ns>[,<ns>...]
           Checkpoint namespaces. Namespaces must be separated by comma.
Currently supported
           namespaces: uts, ipc, mnt, pid, net.

Can I use this to only dump the child process with its pid and net
namespace?

- Hui


On Thu, Jul 30, 2015 at 12:18 PM, Pavel Emelyanov <xemul at parallels.com>
wrote:

> On 07/30/2015 06:57 PM, Hui Kang wrote:
> > Hi,
>
> > (00.004681) Error (namespaces.c:247): Can't dump nested pid namespace
> for 28080
>
> Here's the error. Your task 28078 lives in one pid namespace and its child
> 28080 -- in another. This case is not yet supported by CRIU, all tasks in
> a tree should live in the same pid namespace.
>
> To support multiple pid namespaces we need to resolve tasks' pids in all of
> them, collect this info in the image files and on restore properly clone()
> them into respective pid namespaces.
>
> -- Pavel
>
> > (00.004713) Error (namespaces.c:443): Can't make pidns id
> > (00.004742) Unlock network
> > (00.004772) Unfreezing tasks into 1
> > (00.004799)     Unseizing 28078 into 1
> > (00.004911)     Unseizing 28080 into 1
> > (00.005083) Error (cr-dump.c:1957): Dumping FAILED.
> >
> > Can anyone help? Thanks in advance.
> >
> > - Hui
> >
> >
> >
> >
> > _______________________________________________
> > CRIU mailing list
> > CRIU at openvz.org
> > https://lists.openvz.org/mailman/listinfo/criu
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150730/f68d95d8/attachment.html>


More information about the CRIU mailing list