[CRIU] Live migration for containers - Was "RE: [libvirt] libvirt support for LXC"

Fri Nov 1 17:56:37 PDT 2013

Hello,
  based on the 3D below, it seems that the most logical way to
add support for

	 container live migration

to libvirt is to integrate the latter with CRIU.
If I understand it correctly, Daniel's suggestion below would be
that of
- 1st converting CRIU to a library
- 2nd making libvirt use that library to C/R the container/s

CRIU has recently announced support for

	CRIU as a service

and the reason why they opted for a service instead of a library [1] seems
to be associated with a use case they had:

	ability for an application to invoke a self-dump C/R

In Libvirt's case it would not be the container to ask for a self dump, but it would
be libvirt itself to orchestrate it.

In light of the new CRIU as a service feature, is libvirt's preference still
that of using a library? Would a service be equally good?

Is there anyone actively working or looking at this (libvirt+CRIU)?

Thanks
/Chris

[1]
CRIU: Time and Space Travel Service for Linux Applications
http://www.youtube.com/watch?v=R2Net9eItBc
@37'10'' - CRIU as a system service

> -----Original Message-----
> From: libvir-list-bounces at redhat.com [mailto:libvir-list-
> bounces at redhat.com] On Behalf Of Dmitry Guryanov
> Sent: Wednesday, February 13, 2013 2:58 AM
> To: Daniel P. Berrange
> Cc: libvir-list at redhat.com; criu at openvz.org; Kunal Kushwaha
> Subject: Re: [libvirt] libvirt support for LXC
> 
> On 130207 15:19:08, Daniel P. Berrange wrote:
> > On Thu, Feb 07, 2013 at 03:51:52PM +0530, Kunal Kushwaha wrote:
> > > Hi,
> > >
> > > I am new to this community and am not much aware of current status
> > > libvirt work for LXC.
> > >
> > > Currently I am evaluating LXC with libvirt.
> > > and I found still many features like checkpoint/restore/live
> > > migration ,
> >
> > Checkpoint/restore/migration is something we'd have to delegate to the
> > CRIU code (http://criu.org/LXC). I'm not sure how easy that is todo
> > though, since CRIU code is not a nicely reusable library, it is a set
> > of command line tools. This will need some investigation. I don't
> > believe anyone is actively working on it.
> 
> Please, feel free to contact CRIU development team
> (https://lists.openvz.org/mailman/listinfo/criu).
> 
> We are open for discussion and will help with integration.