The IBM Power product line is a family of servers.
N/A
Oracle VM VirtualBox
Score 9.2 out of 10
N/A
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.
I'd strongly recommend IBM Power servers to anyone who has the budget for it. A Power Virtual Machine, what is generally called FlexTB VM, can support as many small VM of 256GB, and scale up to 32TB on the fly. If IBM recommended architecture is combined with your organizational reference architecture, then forget about running into unplanned downtimes.
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.
A solid IDE for editing programs. SEU was simple and solid. Then it became outdated and support for it ended as the language continued to evolve. That's fine. But RDi is expensive and shaky at best, and VS Code, while free, is severely lacking even the modicum of features RDi has.
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.
This is one of the best systems on the market. You can have Flash/Copy which created another LPAR to look like the system you are copying. This takes seconds and not minutes. Then you can use BRNS to do full system backups nightly with no downtime. I am ready for us to upgrade to a Power 10.
They are very easy to set up and use once you re knowledgeable enough to deal with it. They are continuously enhance the user experience on the HMC and operations on the systems. Once setup it's like a beast, going on and on. I have experience with servers that are not being rebooted for more than 1000 days
Easy and quick to use. Runs at sufficient speed even with 5/6 VMs running, and can handle a bridged network with ease. Easy to disassociate from the host to ensure the environment built within VB is quarantined should anything happen, meaning no risk to physical hardware. Quick to pick up. Quick to add new machines. Cloning feature very quick and comprehensive. I've never had a VM crash or freeze.
In all of the years I have used various Power System, I have never had any problems at all. Even when hackers were attacking our email servers and many users PCs, the IBM Power System came out completely unscathed. I haven't even had any application errors that were able to take the system down. Nor have I ever experienced an unplanned outage
The IBM Power System is built for integration. It supports multiple operating systems and you can run multiple OS's on the same box with no problems at all. It also supports a number of open source languages such as PHP, Java, Python, and Perl which helps you continue to grow and integrate with lots of other systems.
On large-scale systems, the rating would have been 10. However, I have seen some cases in more rural areas where the IBM onsite support is not as available or of the highest quality as in the past. For software support, there are sometimes instances of language barriers.
Systems are robust and you need to know exactly what your are going to do with them. There are multiple configurations possible and you need to gather your requirements first, before going on with the implementation. Tuning is a must before migrating production systems
Power server do not need a stack of software for viruses, spam and others... Power server do not need to have release often power server are much more strong then other manufacturer Power server do not need to restart offen
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
This system can work in a small factory with a few users and easily scale out to thousands of users. It is truly amazing on how much you can throw at this box and it will just keep humming. It is great for use across multiple departments and even across multiple corporations. I worked at one company where we were hosting multiple corporations on just one large Power System and had ZERO problems.
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.
For personal use, there is no monetary investment, I am running 5 CentOS servers flawlessly in my home lab.
Saves a ton of money in an enterprise environment by not having to purchase physical test servers. (Cost of Enterprise product is way lower vs Cost of standing up physical servers and/or cloud servers)
Makes virtualization very easy and friendly for everyone for test instances.
