From: sean <seanlkml@sympatico.ca>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, riel@redhat.com,
garloff@suse.de
Subject: Re: [ANNOUNCE] OpenVZ patch for 2.6.16 and beta SUSE10.1 kernels
Date: Mon, 27 Mar 2006 06:42:03 -0500 [thread overview]
Message-ID: <BAYC1-PASMTP02384285CB847B7D050BABAED20@CEZ.ICE> (raw)
Message-ID: <20060327064203.24f8f607.seanlkml@sympatico.ca> (raw)
In-Reply-To: <20060327112201.GC16409@MAIL.13thfloor.at>
On Mon, 27 Mar 2006 13:22:01 +0200
Herbert Poetzl <herbert@13thfloor.at> wrote:
> also the web pages 'Description of Virtuozzo(tm) benefits over OpenVZ'
> clearly state that:
>
> Virtuozzo(TM) is SWsoft's virtualization and automation solution
> built on top of OpenVZ. Differently from OpenVZ, Virtuozzo(TM)
> is developed and designed to run production workloads in 24×7
> environments and provides significant improvements and additional
> functionality in the areas of stability, density, management tools,
> recovery, and other areas.
Don't think anyone is proposing this for inclusion in mainline.
And I doubt anyone wants a solution in mainline that isn't designed
for production workloads and 24x7 environments, especially if it
has known stability problems.
>
> Specific benefits of Virtuozzo(TM) compared to OpenVZ can be found
> below:
>
> Higher VPS density. Virtuozzo^(TM) provides efficient memory and
> file sharing mechanisms enabling higher VPS density and better
> performance of VPSs.
>
> Improved Stability, Scalability, and Performance. Virtuozzo(TM)
> is designed to run 24×7 environments with production workloads
> on hosts with up-to 32 CPUs.
>
next prev parent reply other threads:[~2006-03-27 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 10:01 Kirill Korotaev
2006-03-27 11:22 ` Herbert Poetzl
[not found] ` <20060327064203.24f8f607.seanlkml@sympatico.ca>
2006-03-27 11:42 ` sean [this message]
2006-04-12 7:58 ` Kirill Korotaev
2006-04-12 13:15 ` Stephen Frost
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=BAYC1-PASMTP02384285CB847B7D050BABAED20@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=akpm@osdl.org \
--cc=garloff@suse.de \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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
Powered by JetHome