From: Stefan Hajnoczi <stefanha@gmail.com>
To: urgrue <urgrue@bulbous.org>
Cc: kvm@vger.kernel.org
Subject: Re: market share??
Date: Tue, 17 Jun 2014 17:07:08 +0800 [thread overview]
Message-ID: <20140617090708.GT16768@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <5399D9CE.7050404@bulbous.org>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Thu, Jun 12, 2014 at 06:48:14PM +0200, urgrue wrote:
> Does anyone have ANY idea where I could find out about market share and
> adoption rates of linux hypervisors (kvm vs xen vs vmware, mainly)?
> I've not found anything despite extensive searching, which is really kind of
> problematic when you're trying to convince the bosses...
A few years ago IDC published this analysis of KVM. A lot has changed
since then but it's fun to look back and read:
http://www-03.ibm.com/systems/resources/systems_virtualization_idc__kvmforservervirtualization.pdf
For example, it says KVM has opportunities in the cloud. Today KVM is
the default and best supported OpenStack hypervisor.
I would focus on more than just KVM (the hypervisor). Consider what
sort of virtualization solution you need. Are you doing server
consolidation inside your organization? Are you doing virtual server
hosting? Are you doing virtual desktop infrastructure?
Then look at the management tools and ecosystem for that problem space.
It doesn't matter how good the hypervisor is if your management tooling
is a pain to use or doesn't support the storage or networking
architecture you use.
Next, evaluate it. KVM is free, try it out, prove it works.
At that point you'll know which choice is right for you.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-06-17 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 16:48 market share?? urgrue
2014-06-17 9:07 ` Stefan Hajnoczi [this message]
2014-06-20 7:32 ` Jidong Xiao
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=20140617090708.GT16768@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=urgrue@bulbous.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