Kernel-based Virtual Machine (KVM) is a virtualization solution developed by small Israeli software company Qumranet and supported by Red Hat since that company's acquisition in 2008.
N/A
VMware Workstation Pro
Score 8.2 out of 10
N/A
VMware Workstation Pro is virtualization software which allows running multiple x86-based operating systems on one PC. Users can run Windows, Linux and BSD virtual machines on a Windows or Linux desktop.
N/A
Pricing
Kernel-based Virtual Machine (KVM)
VMware Workstation Pro
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
KVM
VMware Workstation Pro
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Kernel-based Virtual Machine (KVM)
VMware Workstation Pro
Features
Kernel-based Virtual Machine (KVM)
VMware Workstation Pro
Server Virtualization
Comparison of Server Virtualization features of Product A and Product B
Kernel-based Virtual Machine is very well suited when one needs a single-node virtualization host or needs to build a complex demo setting on their own notebook (e.g. when demonstrating solutions to a customer).
Some scenarios where VMware Workstation pro is best suited are: 1. Utilization for testing software - can install a virtual machine to simulate software requirements and testing it on your network. 2. Testing operating systems upgrades and installation on specific hardware requirements. 3. Virtualizing a physical server 4. Being able to backup a whole server and restore from it in the event of any issue occurring.
Making it easy to export VMS is something that Workstation struggles with; exporting to OVA which is the primary type of VM we export to is cumbersome and can be difficult without proper knowledge on how to do this.
Management of VMS could be a little bit more in depth.
I think the networking portion of Workstation could use some slight improvements, more in-depth segmentation to support containers, however, this is a small issue and not something many people will miss or need.
It does the job and stays out of the way. The specifics of usability relies on the implementation, but with things like Icarus and libvirt, things are standardizing nicely.
It is well documented since it is a long actor in the virtualization scene. Easy to use for most user cases. Pretty much not maintenance on the software besides the occasional software updates and/or compatibility issues from time to time.
I haven't had to call VMware Workstation support. The majority of the time, whenever I have a problem, I can perform an online search and find the answers I need. Online forums and users with similar situations are generally sufficient to answer any questions I have had, though, from previous experience at another company, their support is outstanding and responsive to circumstances. However, that is generally for a paid support contract and should be expected when you are paying for that support.
The key points why I made my decision for KVM in comparison with VMWare are: Freeware software (I am using an Ubuntu server OS), Fewer resources usage, vSwitch using that provides the ability to configure dot1q trunks to/between VMs, Stability, and simplicity of using/troubleshooting, Well-known interface (for Linux geeks).
VMware Workstation does have a price unlike VirtualBox, that is free. But, Workstation Pro makes up for it by how many features comes with it. We are also able to take VM's in our vSphere Production environment and spin it up on and isolated laptop for sandbox testing within Workstation Pro. I'm not sure that VirtualBox is able to do that
The ROI on Workstation would be hard for us to compute. It makes things easier to do and to get access to, but there are other applications and methods to do much the same thing.
Where there has to be a some form of ROI is in the fact that you will actually do things that you might not otherwise do simply because Workstation makes them easier. Sandbox testing is a good example of this idea.