SonuSingh - PeerSpot reviewer
Senior Solution Architect at Micro Focus
Vendor
Simple configuration, helpful support, and intuitive interface
Pros and Cons
  • "I have found KVM to be scalable."
  • "I have previously used VMware and KVM is easier to use. However, they both have their strengths depending on their use cases. They are mostly equal. One of VMware's advantages is it has better support."

What is most valuable?

The most valuable feature of KVM is the hypervisor environment and how we can configure it with ease. Additionally, the interface is intuitive.

For how long have I used the solution?

I have been using KVM for approximately two years.

What do I think about the stability of the solution?

KVM is a stable solution.

What do I think about the scalability of the solution?

I have found KVM to be scalable.

Buyer's Guide
KVM
March 2024
Learn what your peers think about KVM. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
769,479 professionals have used our research since 2012.

How are customer service and support?

The technical support has been good, we are able to receive help for complex environments.

Which solution did I use previously and why did I switch?

I have previously used VMware and KVM is easier to use. However, they both have their strengths depending on their use cases. They are mostly equal. One of VMware's advantages is it has better support.

How was the initial setup?

The initial setup of KVM is simple.

What's my experience with pricing, setup cost, and licensing?

KVM is priced reasonably.

What other advice do I have?

I rate KVM an eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
PeerSpot user
Senior Consultant IT Infrastructure at a tech consulting company with 51-200 employees
Consultant
KVM allows me to run virtualized environments for my customer projects and to modify the code as it's open-source, although there were stability issues when running I/O intensive tasks.

What is most valuable?

KVM runs virtualized guests with its own kernel, which is very important to me.

How has it helped my organization?

I mainly use it for customer projects, as KVM allows running virtualized environments for free in a very efficient way. Furthermore, it is an open source solution so modifying the code is possible. One might think that this is never necessary for most projects; however, when a specific customer requested an enhancement of the functionality, I was able to provide that. The customer was very impressed that KVM is such a professional solution although it is free.

Over the years, many customers were happy that they were able to choose between VMware, Xen and another alternative - KVM.

What needs improvement?

Setting KVM up and running it with dozens of parameters can be annoying. However, there is a control interface called Virsh (and also a GUI called virt-manager) which allows running KVM guests with a simple config file.

For how long have I used the solution?

I have been using KVM since 2010, so for fives years in total.

What was my experience with deployment of the solution?

So far, no issues.

What do I think about the stability of the solution?

When running I/O intensive tasks, or having a very high amount of network packages which need to reach the guest(s). However, all issues were under control after tuning the config of the KVM guests.

What do I think about the scalability of the solution?

No issues yet.

How are customer service and technical support?

There is no customer service, only the community. It is a free product, based on open source software. However, one can use RHEV (the enterprise virtualization product from Red Hat), then you will be able to contact the Red Hat support.

Which solution did I use previously and why did I switch?

I used Xen in the past and switched because the customers requested a solution which allows running a guest with its own Kernel. This is also possible with Xen, but not a common use case, though.

How was the initial setup?

The initial setup, when done manually, is complex because you need to be an experienced Linux user or admin, especially as the networking part can be challenging.

What about the implementation team?

I always deploy it on my own.

What's my experience with pricing, setup cost, and licensing?

It is free! Use it and if you need enterprise support, make sure to use RHEV, the virtualization product from Red Hat.

Which other solutions did I evaluate?

No, because in the open source world, there are not many hypervisors which have the same feature set as KVM.

What other advice do I have?

Make sure to gain a lot of knowledge about virtualization and the way KVM works. Then implement it with libvirt and virt-manager because this makes running KVM guests a lot easier.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user

Interesting responses.
QEMU is the underlying technology for KVM, Xen and Virtualbox.
KVM provides accelerators on top of QEMU, and although KVM does not provide the fancy next>next>done GUI of the others, it provides for fine grained tuning, easier cloud orchestration and the widest range of platform/cpu emulations - and windows runs absolutely fine under KVM, even if you want to run a gaming platform, you can passthrough the video adapter, and access the underlying Linux system via ssh, with surprisingly little performance loss.

Arguments around what is best are subjective and use case is the primary relevance.

Large cloud providers work on standards based deployments - working with 10s of thousands of VMs. OpenStack is the prevailing cloud computing deployment architectural standard. libvirt (qemu/KVM on x86) is the only Hypervisor in group 1, which is 100% compatible with standards and fully supported. Group 2 includes Hyper-v, VMWare, Xen, Group 3 includes docker and LXC.

Large and medium enterprise are on the journey of moving to cloud architectures, and inevitably, they will end up with workload sitting on qemu based hypervisor in the future.
Currently, they typically run VMWare, which was largely responsible for the hypervisor revolution, but computing requirements have grown beyond what can be done 'in house' with a small IT team.

The whole IT industry has grown tremendously in the last 20 years. Large portions of company budgets are consumed by IT expenditure, and with this scale, productivity gains are required to keep IT expenditure under control. Higher utilization, thiner server instances, thiner applications, automation, orchestration, co-location, managed services, outsourcing, transformations, the cloud, IoT. Internal IT teams WILL be reduced to being flight deck administrators, with the hardware and software management being handled by someone else. Someone who has the economies of scale, to do things faster, cheaper and better.

Back to Hypervisors...
The main question is, does your 'server' need a head? Do you need to have a desktop environment and management tools installed in the server? Or can the server have these aspects abstracted from the VM and the tasks performed via APIs? (think about windows server core, or linux). This increases efficiencies in many ways.

If you are looking at virtualization, in the context of running an application interface in a contained operating environment, on your local computer, for whatever reason, the reality is that, those requirements are not the requirements of the industy/enterprise for computing infrastructure that the real hypervisors are being built for.

My advice:
If you want to run your own server, with virtualization, use VMWare free version. Or Xen, or QEMU if you like, whatever you are happy with, and meets your requirements - they can all host windows or linux VMs fine.

If you want to use your desktop/laptop with a few guest vms, run VMWare Player or VirtualBox.
If you're a glutton for punishment, install one of the servers first and passthrough the video card at least, if you're using photoshop or playing a modern game, you'll want the video drivers to have direct access to the card.

And if you want to support IT infrastructure in the future, learn to code, because those days of managing your own DC, installing servers, patching, firewalls, hypervisor GUIs, next next next done jobs, wont be around for ever.

See all 13 comments
Buyer's Guide
KVM
March 2024
Learn what your peers think about KVM. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
769,479 professionals have used our research since 2012.
PeerSpot user
Tech Support Staff with 51-200 employees
Vendor
Possibility of using KVM Virtualization in Hosting

Virtualization has made a lot of progress during the last decade, primarily due to the development of myriad open source virtual machine hypervisors. This progress has almost diminished the barriers between operating systems. There are mainly two types of virtualizations; Software Virtualiztion and Hardware Virtualization. Up until recently, the focus always has been on software­emulated virtualization.


KVM

KVM is short for Kernel­based Virtual Machine and makes use of hardware virtualization, i.e., you need a CPU that supports hardware virtualization, e.g. Intel VT or AMD­V. Connsidering the time line of virtualization techniques, KVM is a relative newcomer. Several incumbent open source methods exist today, such as Xen, Bochs, UML, Linux VServer, and coLinux, but KVM is receiving a surprising amount of exposure now. KVM is a unique hypervisor. It consists of a loadable kernel module that provides the core virtualization infrastructure and a processor specific module. Using KVM virtualization, one can run multiple virtual machines running unmodified Linux or Windows images. Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc. The kernel component of KVM is included in mainline Linux. KVM is a relatively new and simple, yet powerful, virtualization engine, which has found its way into the Linux kernel, giving the Linux kernel native virtualization capabilities. Because KVM uses hardware­based virtualization, it does not require modified guest operating systems, and thus, it can support any platform from within Linux, given that it is deployed on a supported processor.


Advantages of KVM Virtualization


• High Security
• performance and scalability
• Adequate for most cloud deployments
• Simple type­2 hypervisor
• Easy to setup
• Open source software
• Run multiple virtual machines running unmodified Linux or Windows images.
• Each virtual machine will have private virtualized hardware: a network card, disk, graphics adapter, etc
• More flexible compared to other virtualiztion technologies.
• KVM is the best Linux kernel­integrated hypervisor technology.


A typical KVM installation consists of the following components:


• A device driver for managing the virtualization hardware; this driver exposes its capabilities via a character device /dev/kvm.
• A user­space component for emulating PC hardware; currently, this is handled in the user space and is a lightly modified QEMU process.
• The I/O model is directly derived from QEMU's, with support for copy­on­write disk images and other QEMU features.


How to check System Compatibility ?

First, you need a processor that supports virtualization. For a more detailed list, you can refer xensource wiki. You can tell whether your system supports virtualization by looking at /proc/cpuinfo. This file specifies whether the vmx (Intel) or svm (AMD) extensions are supported. A wide variety of guest operating systems work with KVM hypervisor, including many flavours of Linux, BSD, Solaris, and Windows Operating Systems. A modified version of Qemu can use KVM to run Mac OS X.


KVM vs Existing Hypervisors :

In many ways, VMware is a ground­breaking technology. VMware manages to fully virtualize the notoriously complex x86 architecture using software techniques only, and to achieve very good performance and stability. As a result, VMware is a very large and complex piece of software. KVM, on the other hand, relies on the new hardware virtualization technologies that have appeared recently. As such, it is very small (about 10,000 lines) and relatively simple. Another big difference is that VMware is proprietary, while KVM is open source. KVM will, in the long run, greatly benefit from taking advantage of advancements in the kernel, without developers having to re­invent them, as is the case with Xen.

Xen is a fairly large project, providing both paravirtualization and full virtualization. It is designed as a standalone kernel, which only requires Linux to perform I/O. This makes it rather large, as it has its own scheduler, memory manager, timer handling and machine initialization.

KVM, in contrast, uses the standard Linux scheduler, memory management and other services. This allows the KVM developers to concentrate on virtualization, building on the core kernel instead of replacing it.

QEMU is a user­space emulator. It is a fairly amazing project, emulating a variety of guest processors on several host processors, with fairly decent performance. However, the user­space architecture does not allow it to approach native speeds without a kernel accelerator. KVM recognizes the utility of QEMU by using it for I/O hardware emulation.


KVM vs Existing Hypervisors :

KVM

KVM

KVM


Limitations of KVM virtualiation:


• Currently, KVM supports only Intel and AMD virtualization, whereas Xen supports IBM
• PowerPC and Itanium as well. SMP support for hosts is lacking in the current release.
• Performance tuning.


However, KVM already is further ahead than other hypervisor solutions in some areas and surely will catch up in other areas in the future. KVM is the best technology going forward for open source virtualization.

With the introduction of KVM into the Linux kernel, future Linux distributions will have built­in support for virtualization, giving them an edge over other operating systems. There will be no need for any dual­boot installation in the future, because all the applications you require could be run directly from the Linux desktop. KVM is just one more of the many existing open­source hypervisors, reaffirming that open source has been instrumental to the progress of virtualization technology.

The above is a very rough outline of KVM Virtualization, and if you have any questions, we would be happy to talk to you! :)

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user

The CLI on ESXi only can be executed from a windows PC (if you use the free ESXi). The other option is very, very expensive compared with KVM. This is a major reason why I prefer KVM over VMWare. The support of scripting in ESXi free is very limited, in the other hand, KVM works in a normal linux distribution, so, you have all the power of scripting to do what ever you like.

See all 3 comments
Bilal Inamdar - PeerSpot reviewer
Cloud Linux Administrator at a tech services company with 11-50 employees
Real User
Top 5
Stable and scalable solution
Pros and Cons
  • "The initial setup was very easy."
  • "KVM is very difficult to manage and run on daily operations."

What needs improvement?

KVM is very difficult to manage and run on daily operations. It's also too dependent on other solutions and has no backend customization.

For how long have I used the solution?

I've been using KVM for five to six years.

What do I think about the stability of the solution?

KVM's stability is fine, assuming it's running on decent hardware.

What do I think about the scalability of the solution?

KVM is scalable, but it requires a certain amount of technical knowledge to understand how it can scale to other locations.

How was the initial setup?

The initial setup was very easy.

What about the implementation team?

I implemented KVM myself.

What's my experience with pricing, setup cost, and licensing?

KVM is free.

What other advice do I have?

I would give KVM a rating of eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Solution Architect at a comms service provider with 10,001+ employees
Real User
Stable functionality, but implementation could be easier
Pros and Cons
  • "KVM is stable."
  • "In our setup, we do not have any dashboards or orchestration, and it is hard to manage. We have 25 gig network cards, but the software driver we have only supported 10 gigs."

What is our primary use case?

We are using KVM across our company for virtualization.

What needs improvement?

In our setup, we do not have any dashboards or orchestration, and it is hard to manage. We have 25 gig network cards, but the software driver we have only supported 10 gigs.

For how long have I used the solution?

I have used KVM within the last 12 months.

What do I think about the stability of the solution?

KVM is stable.

Which solution did I use previously and why did I switch?

We have used Baremetal.

How was the initial setup?

There are different types of implementations and the current implementation we had, we did not spend enough time to optimize it for a highly demanding production environment. We were not running the most sensitive applications in that environment. Where we needed performance we run Baremetal. In the near future, we are going into cloud-native Kubernetes space as well.

What's my experience with pricing, setup cost, and licensing?

We had some problems with the licensing.

Which other solutions did I evaluate?

We have evaluated Kubernetes.

What other advice do I have?

We have had a lot of problems with the solution but it is not the fault of KVM. It was our fault for not doing a full suite deployment.

I rate KVM a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Co-Founder and CTO at a tech services company with 11-50 employees
Real User
Cost-effective, stable and scalable; support for snapshot and revert could be improved. HA features can be improved.
Pros and Cons
  • "Very cost-effective."
  • "Lacks high availability across clusters as well as support for Apache CloudStack."

What is our primary use case?

We integrate KVM as part of our product. I'm the CTO of our company. 

What is most valuable?

The solution is very cost-effective. VMware is exorbitantly priced and compared with other products KVM is much cheaper especially in the public cloud scenario.

What needs improvement?

Their support for snapshot and revert could be improved. I'd also like to see the product achieve high availability across clusters and to have more support for Apache CloudStack.

For how long have I used the solution?

I've been using this solution for over a year. 

What do I think about the stability of the solution?

We haven't had any issues with stability. 

What do I think about the scalability of the solution?

Scalability is fine, no problems at all. 

How are customer service and technical support?

We have worked with certain support vendors and they're fine. In particular, we work with one of the Red Hat partners and we're quite happy.

How was the initial setup?

The complexity or otherwise of the initial setup depends on the situation but generally it's not too difficult. We offer our customers maintenance support which generally involves update patching.

What's my experience with pricing, setup cost, and licensing?

KVM offers both an open source and licensed version. 

What other advice do I have?

Before deployment, it's worth checking whether the solution fits your use case and how it would be used across various large deployments. Test it before implementing. 

I rate the solution seven out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
PeerSpot user
PeerSpot user
Solution Architect, IT Consultant at Merdasco - Rayan Merdas Data Prosseccing
Real User
Top 10
Good performance, but better management features and integration are needed
Pros and Cons
  • "The GUI interface makes the management of KVM easier than ever before."
  • "Business continuity features need to be added."

What is our primary use case?

We are a consulting company and I work with a lot of solutions to compare them and find out which ones are good for my customers.

The primary use case for this solution is virtualization.

I use this solution in on-premises data centers.

How has it helped my organization?

Compared to other virtualization solutions KVM is much faster and better at managing resources. For example, we compared XEN, KVM, and Vmware for creating development infrastructure for our programmers, we ended up using KVM.

What is most valuable?

The GUI interface makes the management of KVM easier than ever before.

The performance of this solution is great.

What needs improvement?

This solution is lacking in features such as management and integration.

  • This solution needs better integration with desktop virtualization.
  • Better integration with storage solutions is needed.
  • Business continuity features need to be added.
  • The live migration needs to be improved.
  • You cannot run this application in a data center using only the GUI, so you have to have some knowledge with Linux in order to best manage it.
  • Better network management software is needed.
  • Features like vSAN are not available on KVM.
  • Integration with Kubernetes would be an improvement.

Generally, this solution should be made easier to use. Many customers don't have enough experience with Linux or a deep understanding of operating systems, and they just want to use the product. This together with a lack of features has led customers to choose VMware.

For how long have I used the solution?

I have been working with this solution for more than ten years.

What do I think about the scalability of the solution?

This solution is limited in terms of scalability. I think that it is suitable for a mid-range company, but for a larger company, it is not quick. It does not have features for companies that need expandable solutions.

This solution is not used directly by the end-users. If KVM is installed in their data center then they just use the virtual machine. Users don't care about infrastructure, they're just looking for stability and use the operating system for their service. It is the administrators who use this product. Typically, there are two or three administrators in each data center. In terms of end-users, I have seen more than one hundred concurrent users.

How are customer service and technical support?

We do not have access to Red Hat support from our country.

For technical support we depend on the internet and the knowledge of our administrators.

Which solution did I use previously and why did I switch?

I have used XenServer and VMware, and the performance of KVM is better than these.

When it comes to management, integration, business continuity, and live migration, KVM is lacking features and VMware is better in this area.

How was the initial setup?

The initial setup of this solution is not hard, but when you want to use this product in your data center, you have to use the command-line interface to better manage it. You cannot run this application using the GUI alone, so if you don't have enough knowledge with Linux then you may have some trouble.

What about the implementation team?

Most of our solutions are implemented in-house as well as this one.

What's my experience with pricing, setup cost, and licensing?

This solution can be used for free but if you have an expert team on Linux OS, select this one. if you don't have them, forget about it.

Which other solutions did I evaluate?

I evaluate options such as XenServer, VMware, and KVM every six months in order to choose the best product for my customers.

What other advice do I have?

I have been using this solution since before it was owned by Red Hat, when it was community-based. It is easier to manage than ever before because you used to have to use the command-line interface, instead of the GUI.

I do not recommend this product for those looking for a stable and scalable virtualization solution because they will ultimately have problems in their data center. Just two weeks ago, I helped a friend of mine to migrate from KVM to VMware.

I think that if Red Hat worked on some business continuity features and add them to KVM then it would receive a better grade and be a more competitive solution.

I would rate this solution a five out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
IT Manager at a tech vendor with 51-200 employees
Real User
Review about KVM

Valuable Features:

It gives us live VM migrations.

Improvements to My Organization:

It allows us to virtualize our entire IT Infrastructure without any software cost. We only need to spend money on support and deployment.

Use of Solution:

Used since 2009 from version 0.8, so 6 years now.

Deployment Issues:

No.

Stability Issues:

No.

Scalability Issues:

It's scaled for us since version 0.8.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user