Open source, cross-platform, virtualization software that enables developers to deliver code faster by running multiple operating systems on a single device, used to deploy applications on-premises and to the cloud. Oracle VM VIrtualBox is Oracle's cross-platform virtualization offering, acquired with Sun Microsystems in early 2010. The software was originally developed by Innotek GmbH.
N/A
VMware vSOM (discontinued)
Score 10.0 out of 10
N/A
VSOM from VMware was a solution that delivered vSphere server virtualization, and also added capacity management and performance monitoring features. It is discontinued as of February 2019. Users were migrated to VMware vSphere Enterprise Plus and VMware vRealize Operations Standard.
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.
Vsphere Operation Management is suitable for automating the process of bringing up an alternate data center in case of a disaster. It also is a great way for testing your readiness of disaster. You have the ability to bring up a server in a "bubble" for testing. This way you can show your admins how the failover process will work.
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.
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
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
vSphere with Operations Management has a much better way of automating the re-IPing of servers so you can stand them up in a different environment or location. You do, however, need another way of replicating your servers to your DR site, VSOM will not do that. We used EMC Recover Point for replication.
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).