Discussion on:

6
Comments

Join the conversation!

Follow via:
RSS
Email Alert
0 Votes
+ -
Thank you; this is an area of intense interest for us. We have been very happy using VServer rather than OpenVZ and thus are very interested to know how LXC compares with VServer on several fronts.

Resource utilization:
The hashify feature of VServer is a life saver for systems with many similar virtual servers (containers). It takes duplicate files in the file system between containers and replaces them with immutable hard links maintaining only one actual copy. The disk space savings can be enormous. Is there anything like this in LXC?

Capabilities:
The fine grained tuning of capabilities, what can and cannot be done in a container, is a great feature of VServer. Is there this kind of control in LXC?

Memory Consolidation:
We are very interested in how KSM will play with both VServer and LXC. Can it be used to consolidate memory between containers within LXC?

Thanks again. This is very helpful - John
0 Votes
+ -
Good questions
vdanen 27th Feb 2010
Good questions. I don't know the answers to them off-hand. =) LXC is still quite new and not as feature rich as OpenVZ or, I imagine, VServer (which I've never used). I don't think LXC is yet production-ready -- I wouldn't change to using LXC on a VPS over OpenVZ/Virtuozzo, for instance. At least not yet. With the pace of development and it being included upstream, expect it to make significant gains of usability and "polish" in the near future.

But sorry, I can't answer those specific questions off the top of my head.
Actually openvz is available directly from my distro vendor - out of the box, as debian and ubuntu both support openvz. Just a simple apt-get, a reboot into the openvz kernel, and we're ready to start creating containers.
0 Votes
+ -
certain distros
vdanen 27th Feb 2010
Sure, some distros would have OpenVZ support in them by doing the patchwork themself. Not all distributions do. With LXC being part of upstream, all vendors can provide LXC support with minimal effort.
0 Votes
+ -
The OpenVZ kernels provided by Ubuntu and Debian have always been based on devel branches of the OpenVZ kernel rather than the stable branches... which are RHEL4 and RHEL5 based. As a result, fixes and features have always lagged behind in the devel branches and Debian especially has often had rather outdated versions of the OpenVZ userspace tools... although I hope they are caught up by now.

The future looks brighter though because the OpenVZ Project head said that they are working on a new stable branch based on 2.6.32 which is the kernel that will be in the next Debian, Ubuntu and RHEL releases. They hope to get it done prior to the release of the next Debian... and most surely before RHEL6 which is due sometime this summer. Whether that will pan out remains to be seen. I certainly hope it does.

I also hope that LXC matures and the userspace tools for it mature so even more people can take advantage of containers with them being supported in the mainline kernel.

The OpenVZ Project's goal has always been to get containers into the mainline so they could stop maintaining such a large, third-party patch that has no way of getting into mainline itself.
You are wrong. If running a recent Debian, such as squeeze, no openVZ kernel.
Also have a look at that discussion: http://openvz.org/pipermail/users/2010-January/003189.html
Keyboard Shortcuts:
Prev
Next
Toggle
Join the conversation
Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

Join the TechRepublic Community and join the conversation! Signing-up is free and quick, Do it now, we want to hear your opinion.