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
Oracle VirtualBox
Score 8.8 out of 10
N/A
Oracle VirtualBox is an open source, cross-platform, virtualization software, enables developers to deliver code faster by running multiple operating systems on a single device.
$0
per month
Pricing
Kernel-based Virtual Machine (KVM)
Oracle VirtualBox
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
KVM
Oracle VirtualBox
Free Trial
No
No
Free/Freemium Version
No
Yes
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)
Oracle VirtualBox
Considered Both Products
KVM
Verified User
C-Level Executive
Chose Kernel-based Virtual Machine (KVM)
Kernel-based Virtual Machine is an open-source and free solution, compared to Virtualbox which is a product from Oracle.
Compared to VirtualBox, KVM has simpler licensing terms and is supported by the operating system vendor. KVM also has more mature integrations with other open-source projects. Automating provisioning is simple with KVM since it is available in the package repositories of …
KVM is free and provides environments where guests can run their own Kernel while still performing very well. It is also very native to work with KVM since it is integrated within the Linux Kernel.
Oracle VirtualBox is the better choice due to its cost-effectiveness, ease of use and feature set. However VMware Workstation is more suitable due to its superior performance, better features and better integration with enterprise tools. VMware Workstation also provides a …
I've worked and taught in many environments where the OS used by others (or by me for employment reasons) is a mix of Windows and Mac OSX. Sometimes Linux is around if I can help it. Being familiar with VirtualBox means I won't …
I have used Linux KVM and Oracle VirtualBox in order to virtualize and manage different VMs. Oracle's solution, in my opinion, it is better because of the GUI, documentation and API. I have managed to write scripts to automate different procedures to help in my daily duties. I …
KVM is the best solution in the case you need to test and turn up any virtual environment with limited vCPU/RAM resources. The obvious area of its use is a network environment when we want to avoid being tied to one type of hardware/vendor and being able to swap from one instance to another with no downtimes. The use of a vSwitch (that supports VLAN tagging) is a significant bonus for network engineers that some other hypervisors do not provide.
It is best suited when you want to have different operating systems on your laptop or desktop. You can easily switch between operating systems without the need to uninstall one. In another scenario, if you expect some application to damage your device, it would be best to run the application on the VM such that the damage can only be done to the virtual machine. It is less appropriate when time synchronization is very important. At times the VMs run their own times differently from the host time and this may cause some losses if what you doing is critical. Another important thing to take note of is the licensing of the application you want to run your VM. Some licenses do not allow the applications to be run on virtual servers so it is not appropriate to use the VM at this time.
I have had issues in the past when it has come to resizing VM disk storage. The issue is entirely detailed here: https://www.virtualbox.org/ticket/9103 -- the problem was caused because of having existing snapshots (which error message output was not detailing). I haven't had to deal with the issue due to my dynamic disk sizes not being small from the start anymore (this is mostly an issue for my Windows VMs where the base disk may need significant size for the OS). It looks like, for a resize, that a merge of all snapshots has to occur first -- one user on that list details a workaround to maintain snapshots by cloning the VM. (Note: 5.2 was just released a few weeks ago, and looks like it should prevent the problem happening in the future by properly informing users that it isn't possible with snapshots).
Certain scenarios, like resizing disks, required dropping into a terminal as there were no options to previously do so via the GUI. According to some recent posts, I've seen that v5.2 has added disk management stuff like that to the GUI (or will be adding it). I'm comfortable with dropping into the terminal, but in a teaching scenario or when evaluating the learnability of the tools, it complicates things.
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.
I love using the Graphical User Interface. The VirtualBox Manager is very easy to understand and use. You can quickly create, configure and manage all your virtual machines in one window. It makes operating virtual machines easy and simple. When using VBoxManage it gives the user comprehensive control over VirtualBox so that you can use automation and scripting at the command-line interface
It is a very reliable solution that can be used for x86 architecture virtualization with low overhead. It is a free and open source software. Easy to use withOpenStack.
VirutalBox is very similar to using Vmware with the slight difference in appearance and what might be considered a less polished look. However, what it lacks in polish and looks it makes up for in functionality, easy of use and the wide range of operating systems and features it supports without the need of buying the full professional edition
The only problem I have found is that the deployment is dependent and intrinsically linked to the Host OS. This is different from bare metal solutions which remove that dependency on a Host OS. The latter is more reliable and removes a layer of potential failure.
Minimal-to-no support needed from the DevOps team.
Provides a direct and an easy way to access multiple VMs inside the same machines which enables performing various testing and QA tasks without the need to switch hardware.
Automatic provisioning using tools (esp. Vagrant) which enables developing a base image once, and allows for exporting/importing anywhere across the developers team.
Very cost-effective (no fees or monthly subscriptions).