[CRIU] [PATCH] p_haul_iters: use self.htype.can_migrate_tcp as function
Pavel Emelyanov
xemul at parallels.com
Thu Apr 10 10:08:30 PDT 2014
On 04/10/2014 05:52 PM, Andrey Vagin wrote:
> Signed-off-by: Andrey Vagin <avagin at openvz.org>
> ---
> p_haul_iters.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/p_haul_iters.py b/p_haul_iters.py
> index c6cbfb0..31a1c74 100644
> --- a/p_haul_iters.py
> +++ b/p_haul_iters.py
> @@ -156,7 +156,7 @@ class phaul_iter_worker:
> req.opts.file_locks = True
> req.opts.evasive_devices = True
> req.opts.link_remap = True
> - if self.htype.can_migrate_tcp:
> + if self.htype.can_migrate_tcp():
> req.opts.tcp_established = True
>
> cc.send_req(req, False)
>
Ah, I see :) This explains why dump/pre-dump handled TCP successfully.
So, what is left is to resolve the way we want pid driver to live-migrate
tasks with TCP.
Oscar, can you tell us more about your use-case? What kind of tasks you
plan to live-migrate with p.haul, so that we could better understand what
we can do with IP address.
Thanks,
Pavel
More information about the CRIU
mailing list