public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Peter Chacko <peterchacko35@gmail.com>,
	Emmanuel Noobadmin <centos.admin@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: ESXi, KVM or Xen?
Date: Sat, 03 Jul 2010 09:32:51 +0200	[thread overview]
Message-ID: <4C2EE7A3.5050609@web.de> (raw)
In-Reply-To: <AANLkTimeyKdFtVBPPFI6BeSFROQ6izWwl9C4Iqm7fPVR@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

Peter Chacko wrote:
> Did you consider VirtualBox ? Of course VmWare is the market leader
> NOW, but if you plan to invest on future open source  platforms, You
> should choose KVM(which is now Linux native) or XEN.( Its unlikely to
> be killed). KVM still lag behind in terms of enterprise-class features
> , but count on it for future investment. So, i think you should just
> start off with Xen or virtualBox, with a migration plan to KVM in
> future.

VBox has surely its strengths on non-Linux hosts and hosts without
virtualization acceleration. But I would carefully evaluate its
performance under relevant load:

http://permalink.gmane.org/gmane.comp.emulators.virtualbox.devel/2796


I recently learned from someone doing Xen consulting that it's still
troublesome to get it running on non-certified hardware. This may have
impact on the hardware choice.


For hosting Linux-on-Linux, I would also consider containers, e.g. lxc
or OpenVZ. Performance-wise, that's generally the most efficient approach.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2010-07-03  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03  3:55 ESXi, KVM or Xen? Emmanuel Noobadmin
2010-07-03  4:05 ` Peter Chacko
2010-07-03  7:32   ` Jan Kiszka [this message]
2010-07-03  4:35 ` Javier Guerra Giraldez
2010-07-03  5:48   ` Emmanuel Noobadmin
2010-07-03  7:34     ` Jan Kiszka

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=4C2EE7A3.5050609@web.de \
    --to=jan.kiszka@web.de \
    --cc=centos.admin@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=peterchacko35@gmail.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