mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Kirill Korotaev <dev@sw.ru>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, kir@sw.ru,
	devel@openvz.org, saw@sawoct.com, dim@sw.ru, st@sw.ru
Subject: Re: [ANNOUNCE] first stable release of OpenVZ kernel virtualization solution
Date: Tue, 6 Dec 2005 14:20:53 +1100	[thread overview]
Message-ID: <20051206142053.17793440.akpm@osdl.org> (raw)
In-Reply-To: <43949155.5060606@sw.ru>

Kirill Korotaev <dev@sw.ru> wrote:
>
> Hello,
> 
> We are happy to announce the release of a stable version of the OpenVZ 
> software, located at http://openvz.org/.
> 
> OpenVZ is a kernel virtualization solution which can be considered as a
> natural step in the OS kernel evolution: after multiuser and 
> multitasking functionality there comes an OpenVZ feature of having 
> multiple environments.

Are you able to give us a high-level overview of how it actually is
implemented?  IOW: what does the patch do?

> ...
> 
> As virtualization solution OpenVZ makes it possible to do the same 
> things for which people use UML, Xen, QEmu or VMware, but there are 
> differences:
> (a) there is no ability to run other operating systems
>      (although different Linux distros can happily coexist);
> (b) performance loss is negligible due to absense of any kind of
>      emulation;
> (c) resource utilization is much better.

What are OpenVZ's disadvantages wrt the above?

> The dynamic assignment of resources in OpenVZ can significantly improve 
> their utilization. For example, a x86_64 box (2.8 GHz Celeron D, 1GB 
> RAM) is capable to run 100 VPSs with a fairly high performance (VPSs 
> were serving http requests for 4.2Kb static pages at an overall rate of 
> more than 80,000 req/min). Each VPS (running CentOS 4 x86_64) had the 
> following set of processes:
> 
> [root@ovz-x64 ~]# vzctl exec 1043 ps axf
>   PID TTY      STAT   TIME COMMAND
>     1 ?        Ss     0:00 init
> 11830 ?        Ss     0:00 syslogd -m 0
> 11897 ?        Ss     0:00 /usr/sbin/sshd
> 11943 ?        Ss     0:00 xinetd -stayalive -pidfile ...
> 12218 ?        Ss     0:00 sendmail: accepting connections
> 12265 ?        Ss     0:00 sendmail: Queue runner@01:00:00
> 13362 ?        Ss     0:00 /usr/sbin/httpd
> 13363 ?        S      0:00  \_ /usr/sbin/httpd
> 13364 ?        S      0:00  \_ /usr/sbin/httpd
> 13365 ?        S      0:00  \_ /usr/sbin/httpd
> 13366 ?        S      0:00  \_ /usr/sbin/httpd
> 13370 ?        S      0:00  \_ /usr/sbin/httpd	
> 13371 ?        S      0:00  \_ /usr/sbin/httpd
> 13372 ?        S      0:00  \_ /usr/sbin/httpd
> 13373 ?        S      0:00  \_ /usr/sbin/httpd
> 6416 ?        Rs     0:00 ps axf

Do the various kernel instances share httpd text pages?


  reply	other threads:[~2005-12-06  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 19:13 Kirill Korotaev
2005-12-06  3:20 ` Andrew Morton [this message]
2005-12-06 15:39   ` Kirill Korotaev
2005-12-10 11:22 ` Philippe Pegon

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=20051206142053.17793440.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dev@sw.ru \
    --cc=devel@openvz.org \
    --cc=dim@sw.ru \
    --cc=kir@sw.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@sawoct.com \
    --cc=st@sw.ru \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®