Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	Enrico Weigelt <weigelt-EU+a56NjgY8@public.gmane.org>
Subject: Re: Containers vs. OpenVZ
Date: Tue, 17 Aug 2010 20:59:46 -0400	[thread overview]
Message-ID: <4C6B3082.2070802@cs.columbia.edu> (raw)
In-Reply-To: <20100818002416.GG3648-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>



On 08/17/2010 08:24 PM, Matt Helsley wrote:
> On Tue, Aug 17, 2010 at 12:33:40PM +0200, Enrico Weigelt wrote:
>>
>> Hi folks,
>>
>>
>> could anyone please point out the difference main difference
>> between linux-containers and openvz ? It is possible to replace
>> ovz by linux-containers yet ?
>>
>> thx
>
> Hi,
>
> 	At the very least there is no kernel code in mainline for
> checkpoint/restart of containers at this time. We're still working on
> patches for that feature. So that's one major difference between
> "linux-containers" and openvz.

To be fair, there is not kernel code in mainline for openvz either...

Oren.

>
> 	I'm sure there are other differences which openvz and lxc folks
> can point out but this is the one I'm presently most-keenly aware of. I
> haven't had time to follow what's new with openvz so I'll leave the
> rest of the comparison to other folks.
>
> Cheers,
> 	-Matt Helsley
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
>

  parent reply	other threads:[~2010-08-18  0:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 10:33 Containers vs. OpenVZ Enrico Weigelt
     [not found] ` <20100817103339.GA8495-q9I3ByPDOfiE+EvaaNYduQ@public.gmane.org>
2010-08-18  0:24   ` Matt Helsley
     [not found]     ` <20100818002416.GG3648-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-08-18  0:56       ` Whit Blauvelt
2010-08-18  0:59       ` Oren Laadan [this message]
     [not found]         ` <4C6B3082.2070802-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-08-18 10:42           ` Marc Aymerich
     [not found]             ` <AANLkTinLMVV21pW_icDriWbrZ1U8NgfKYWMhFLBD5XS--JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-18 10:48               ` Marc Aymerich
     [not found]                 ` <AANLkTimHdaZnB-q6_XgoAwxKAwQKgAMtz0_J78MBDBbp-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-18 16:00                   ` Oren Laadan
2010-08-18 17:02               ` Matt Helsley
     [not found]                 ` <20100818170256.GA3642-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-08-23  7:44                   ` Pavel Emelyanov
     [not found]                     ` <4C7226EA.5020600-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2010-08-23  9:08                       ` [Devel] " Peter Volkov
2010-08-23  9:38                         ` Pavel Emelyanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C6B3082.2070802@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=weigelt-EU+a56NjgY8@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox