How Server Virtualization Has Been Influencing The Industry
The server virtualization has been among the most influential technologies since the last decade.
Modern contemporary hypervisors such as VMware ESXi and Microsoft Hyper-V permits a physical server to host multiple virtual machines; the hypervisor offers capabilities that were once unheard of. For instance, it is possible to migrate a running virtual machine from one host to another, without having any downtime.
It is also possible to dynamically allocate hardware resources to virtual machines on the basis of generated need. Approximately, fifteen years back, server virtualization was quite different.
The mainstream adoption of virtualization has occurred only during last few years. The company VMware allows many operating systems to run simultaneously on a single server falls under this category.
VMware’s software, deploy virtualized operating systems. Below shown are snapshots of the random screen capture from a relatively recently done VMware deployment. It acts as a frame of reference for the benefit of those who are not VMware administrators.
Above displayed is the VMware Web client.
Here displayed is the box looked like for VMware 2.0. The most important thing about the box cover is that VMware was designed and deployed to run on top of Windows NT or Windows 2000. This actually was not a bare metal hypervisor, rather an emulation layer.
This picture is the box from VMware 2.0. and how the back of the box looks like.
Observe the references of the long extinct operating systems like, Windows 3.1, Windows 95, and MS-DOS 6.0.
While zooming at the back of the box, we can observe that even in version 2.0, VMware had the capability to pause and resume virtual machines. It was interesting to note that the Disk Management section referenced to non-persistent disks, persistent disks, and undoable disks. These all are still used today.
The virtual disk snapshots and the capability to pause and resume virtual machines is supported by VMware 2.0.
And the hardware requirements for VMware 2.0 were:
A 266 MHz Pentium II
10Mb of disk space
96Mb of RAM, with 128 MB recommended
A 256 color display
500Mb of space for storing guest operating systems
These mentioned were the hardware requirements for VMware 2.0.
What regarding the installation media? Shown below is a picture of the installation CD. There isn’t anything super unique regarding it aside from the fact that it consists of a copyright date of 2000.
This shown is the VMware installation CD.
And the unique part of this fact was that VMware 2.0 consists of a second CD. This second CD consists of ready to run virtual machines which were preinstalled with SuSE Linux 6.3 and TurboLinux Workstation 6.0. And the CD
claims that user can have a Linux VM up and running in few minutes.
Please note that VMware used to offer pre-configured Linux virtual machines.
One last novelty which was observed in the box was a printed instruction manual.
VMware 2.0 consisted of a printed instruction manual.
In case the user is not equipped with any legacy hardware at their disposal and got to install VMware 2.0. then user had to jump through a few hoops, however, eventually will be able to install.
The VMware was installed on the top of Windows Server 2012 R2 inside of a Hyper-V virtual machine. Note how colorful the VMware icon was.
Now here’s few thing that you didn’t find them today. It is the VMware inside of a Hyper-V virtual machine!
When I began VMware for the first time, I was directed to run the Configuration Wizard. The Configuration Wizard takes you through the process of configuring a virtual machine
To configure virtual machines, VMware used a Configuration Wizard.
Upon propelling of the Configuration Wizard, a list of guest operating systems appeared on the screen, to choose from. After spending the little time playing with the software, I observed that VMware automatically allocate resources like, memory, based on my selection.
The Configuration Wizard offers a list of ancient operating systems.
The Configuration Wizard ask several questions related to the location of the virtual machine directory, whether to use a virtual disk or a physical disk, whether or not to capture the CD-ROM, the virtual disk size and what kind of networking to use.
This is different from today, aside from the references to CD-ROMs, and the conspicuous lack of a choice to change the amount of memory which is assigned to virtual machines. You might see a configuration summary below.
Shown above is the configuration summary for a virtual machine.
After making a virtual machine, I was taken over to the console. VMware 2.0 offers a dedicated interface for each virtual machine.
The concept of a centralized was found missing, vCenter like management tool which allowed interaction with the entire collection of virtual machines. Rather, each virtual machine was present within its own separate window.
Above shown how a virtual machine used to look like.
This was an attempt to begin the virtual machine caused the VMware Software to crash due to running on an unsupported version of Windows.
Though it is interesting to take a look back at legacy technology, there is an important point to be made. During the last fifteen years, server virtualization has boomed and grown up. It has evolved to far more feature rich and became more stable.
In fact, most enterprises run mission-critical sensitive workloads within virtual machines. In case you tried out virtualization years ago, however, had a bad experience with it, then it’s probably worth taking your time to give another try with modern virtualization technologies.
The hypervisors of today barely have conventional pitfalls, rather you are surely going to experience accelerated organizational performance.