From: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Peter Volkov <pva-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [Devel] Re: Containers vs. OpenVZ
Date: Mon, 23 Aug 2010 13:38:02 +0400 [thread overview]
Message-ID: <4C72417A.6060005@parallels.com> (raw)
In-Reply-To: <1282554513.2701.50.camel@tablet>
On 08/23/2010 01:08 PM, Peter Volkov wrote:
> В Пнд, 23/08/2010 в 11:44 +0400, Pavel Emelyanov пишет:
>> And no - you cannot replace openvz with lxc yet for many reasons.
>
> Pavel, I think lot's of people will benefit if you summarize important
> points of differences. Yea, I have my own list but I'd better listen to
> knowledgeable people first ;)
:)
OK, but first of all - the list I provide is just the situation we currently
have that will change in the future, not some fundamental problem. Besides, I
can be not aware of some recent changes, so please correct me if I'm wrong.
So, the benefits of the OpenVZ against LXC.
1. Checkpointing. That's the biggest difference.
2. Resource management. Currently in LCX you may only have a per container
user memory management. In OpenVZ we control much more resources like
kernel memory or networking buffers
3. Entering a container. I've seen many approaches of how to join a foreign
container (sys_hijack, sys_nsfd, sys_cloneat, etc) but AFAIK none of them
is included in the mainline.
4. 2-level disk quota. We're trying to push one into the Al's tree however ;)
5. Bells-and-whistles like NFS/NFSd virtualization, FUSE virtualization, etc
6. Containers management like vzlist tool or various /proc files, that help
you to track containers state and resources
> With best regards,
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
prev parent reply other threads:[~2010-08-23 9:38 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
[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 [this message]
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=4C72417A.6060005@parallels.com \
--to=xemul-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=pva-aBrp7R+bbdUdnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.