Any counter-comments, from a VServer strengths point of view?
----- Forwarded message from Kir Kolyshkin <email@example.com> -----
From: Kir Kolyshkin <firstname.lastname@example.org>
Date: Tue, 06 Dec 2005 17:17:18 +0300
Subject: Re: [Users] VServer vs OpenVZ
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
My view of subject is definitely biased towards OpenVZ, but still: there
are areas where OpenVZ is definitely more developed than VServer. Let me
concentrate on three of these.
First is stability. By sticking to old (currently 2.6.8) kernel and
backporting all the bug fixes, security fixes and hardware driver
updates, we make OpenVZ kernel very stable. We do a lot of kernel
testing in house, including stress testing.
Second is resource management. There are a lot of resources that can be
abused from inside VServer guest or OpenVZ VPS, leading to at least DoS;
some of those resources are not under control of traditional UNIX means
such as ulimit. In OpenVZ we have User Beancounters (UBC for short),
which accounts and limits about 20 of such resources (including IPC
objects, various kernel buffers etc).
Third is virtualized network stack. AFAIK VServer's ngnet is not yet
ready for prime time yet, while OpenVZ's venet is here. Without fully
virtualized network stack people are experiencing problems like this one:
Kir, OpenVZ project leader
Eugen Leitl wrote:
>Before I try OpenVZ I would like to hear comments of people
>who've ran both VServer and OpenVZ, preferrably on the same
>hardware, on how both compare.
>Factors of interest are stability, Debian support,
>hardware utilization, documentation and community support,
>My planned usage is VServers in a hosting setting.
Users mailing list
----- End forwarded message -----
-- Eugen* Leitl leitl http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE
Vserver mailing list