Virtualization has always fascinated me, and have always wanted to take a big step with it. Virtualization marks its consideration for many reason few among them is ease in usage, configuration and deployment. My investment of 4 days on virtualization and products supporting and offering services was a real worth. I used major products of virtualization like VMware (player and workstation) , Windows Virtual PC and Sun Virtual Box. All these products haave some merits and demerits. For me to share my experience a better way and to scale the virtualization products, let’s consider a case.
Case:-
1. Setup of the virtual LAB environment, with operating systems ranging from Win XP 2000 to Win Vista and Solaris.
2. All the Machines can be run together and be on internet.
3. Setup can be managed via a single interface.
4. Setup can be reconfigured as per requirement easily and should be high in performance and less on resource consumption i.e. ease in changing networking type, size of the virtual disk, runtime additions etc.
5. No fresh installation of the Operating System, a virtual machine should be created from the host running(a replica of the host machine).
6. Usage of free to use features of the products and no cost involved, except, time.
Tools Used:-
1. Symantec Backup exec system recovery 8.5.
2. Microsoft Virtual PC 2007.
3. VMware Player 2.5.3 build-185404 and VMware Workstation.
4. Sun Virtual Box 3.0.8.
Creating the Virtual Machine from Host: -
As per our requirement number of 5 mentioned above, I had to make the virtual machine of and from the host. To do this I preferred Symantec Backup exec, because it offers me lot of option and easy to use interface. The compatibility support of Symantec Backup Exec is very impressive.
As per the requirement I considered only the primary partition of the Host machine to create a replica virtual machine. The first step is to create the One time Back of the Primary drive of the host operating system using the features of Symantec Backup exec:-
Its pretty straight forward, just select the drive name the output file & the location to store, that’s it., time for coffee. The backup will take time as per the size of the disk. But Here is the best part Backup exec is very smart, the size of the backup file will be similar to the space consumed by information on the physical disk, but can keep record of the total size of the physical disk. The backup file will be saved as .sv2i config file and .v2i virtual hard disk and the best part one can directly run the .sv2i config file on VMware player so the task completes here.
Only major limitation of the Symantec Backup exec during the above process is that it doesn't do the disk checking, if the physical disk has trouble so would the virtual hard disk. I would love to be wrong on this. Symantec Backup Exec is far superior product than Symantec Ghost, easy to use and nice management console all features and options are properly managed.
But I had to opt for the better options as VMware take too much resources and tries to convert the .sv2i file into it readable format and most of the time it fails. Hard to guess who is the culprit. So once the backup file is up, let’s move ahead and use another cool feature of the Symantec Backup Exec system recovery which converts the backup file to virtual hard disk.
The one time virtual conversion feature allows to make choice between VMware virtual hard disk and Microsoft Visual Hard disk. Just make the choice name the output file and location & wait for sweet creation of the virtual hard disk.
if VMware virtual disk is considered :-
One can easily create the VMware machine using VMware workstation linked to the VMware hard disk and use the VMware player to run it. Both VMware workstation and VMware player is required as per our 6th requirement, not to shed any money & VMware workstation is paid software, but trial will do the business required.
if Microsoft Virtual Hard disk is considered:-
Likewise VMware virtual disk create the same for Microsoft Virtual PC and configure virtual machine. One can easily configure the machine and run it with great ease. The Virtual hard disk can also be used with VMware player but it needs to be converted in accordance to its requirement but with no success guaranteed.
Sun Virtual Box :-
The sun virtual box shows very good compatibility for Microsoft virtual hard disk formats & comparatively better performance. But the Sun virtual box supports only one primary hard disk on the management console so no matter how many virtual machine created it will be linked to only one bootable primary virtual hard disk. Can’t ask for better limitation.
Once the Virtual machine is setup repeat the above method to create different virtual machine easily or else copy paste the machine incase required. Thus if there is a test setup of interacting and highly configured machines. The above process can easily create the required backup and create a virtual lab in less effort with high preserving. No information loss, no application configuration changed but all made virtual.
Now let’s look at to the Virtual players and their feature which can help in deciding which virtual machine player and management application can be used to maintain the virtualized setups.
VMware Player and Workstation :-
VMware applications and tools have been a disappointment for me when it comes to the performance of the virtual machines. The virtual machines were running slow on the VMware player, secondly VMware workstation was paid and I had to let if off. VMware installs lot information and tools on the host PC to give the virtualization feel, like separate virtual network adapter and device installations but none were able to give good network performance to the virtual machines, I had created. VMware is still a good choice when considered for ease of use and multiple virtual machine management.
Microsoft Virtual PC 2007:-
Microsoft Virtual PC has most easy to use interface to setup and run the virtual machines. Multiple Virtual machines can be easily managed from a single console. But like the Host Microsoft PC trouble, if the network connection has hiccups so is the operating system. Microsoft Virtual PC doesn't installs the any virtual network adapters as a device along (that u see in network management window) to virtualize host network connections. The concern of performance can be overlooked up to some extent compared to the ease of use and management of many virtual machines.
Sun Virtual Box:-
When it comes to the performance Sun Virtual box should be scored higher compared to it big competitors mentioned above. The Virtual machine performs well over network by impressive virtualization of the network adapter. The virtual resources management of Sun Virtual Box manages Microsoft Windows operating system better than the Microsoft Virtual PC 2007. But after all the goods, sun virtual Box allows only one primary virtual hard disk, so no matter how many virtual machine created they would be using the same virtual HD to boot i.e. better run one machine at a time. To make the situation worse to switch the machine u need to reload it or reconfigure it on the management console, why would someone should take so much of pain, when virtualization should make things easy ?
When acceptance is solution: -
I need ease of Microsoft Virtual PC, performance of Sun Virtual Box and features of VMware. Currently I am considering Microsoft Virtual PC overall for its advantages minus performance hiccups.
Case:-
1. Setup of the virtual LAB environment, with operating systems ranging from Win XP 2000 to Win Vista and Solaris.
2. All the Machines can be run together and be on internet.
3. Setup can be managed via a single interface.
4. Setup can be reconfigured as per requirement easily and should be high in performance and less on resource consumption i.e. ease in changing networking type, size of the virtual disk, runtime additions etc.
5. No fresh installation of the Operating System, a virtual machine should be created from the host running(a replica of the host machine).
6. Usage of free to use features of the products and no cost involved, except, time.
Tools Used:-
1. Symantec Backup exec system recovery 8.5.
2. Microsoft Virtual PC 2007.
3. VMware Player 2.5.3 build-185404 and VMware Workstation.
4. Sun Virtual Box 3.0.8.
Creating the Virtual Machine from Host: -
As per our requirement number of 5 mentioned above, I had to make the virtual machine of and from the host. To do this I preferred Symantec Backup exec, because it offers me lot of option and easy to use interface. The compatibility support of Symantec Backup Exec is very impressive.
As per the requirement I considered only the primary partition of the Host machine to create a replica virtual machine. The first step is to create the One time Back of the Primary drive of the host operating system using the features of Symantec Backup exec:-
Its pretty straight forward, just select the drive name the output file & the location to store, that’s it., time for coffee. The backup will take time as per the size of the disk. But Here is the best part Backup exec is very smart, the size of the backup file will be similar to the space consumed by information on the physical disk, but can keep record of the total size of the physical disk. The backup file will be saved as .sv2i config file and .v2i virtual hard disk and the best part one can directly run the .sv2i config file on VMware player so the task completes here.
Only major limitation of the Symantec Backup exec during the above process is that it doesn't do the disk checking, if the physical disk has trouble so would the virtual hard disk. I would love to be wrong on this. Symantec Backup Exec is far superior product than Symantec Ghost, easy to use and nice management console all features and options are properly managed.
But I had to opt for the better options as VMware take too much resources and tries to convert the .sv2i file into it readable format and most of the time it fails. Hard to guess who is the culprit. So once the backup file is up, let’s move ahead and use another cool feature of the Symantec Backup Exec system recovery which converts the backup file to virtual hard disk.
if VMware virtual disk is considered :-
One can easily create the VMware machine using VMware workstation linked to the VMware hard disk and use the VMware player to run it. Both VMware workstation and VMware player is required as per our 6th requirement, not to shed any money & VMware workstation is paid software, but trial will do the business required.
if Microsoft Virtual Hard disk is considered:-
Likewise VMware virtual disk create the same for Microsoft Virtual PC and configure virtual machine. One can easily configure the machine and run it with great ease. The Virtual hard disk can also be used with VMware player but it needs to be converted in accordance to its requirement but with no success guaranteed.
Sun Virtual Box :-
The sun virtual box shows very good compatibility for Microsoft virtual hard disk formats & comparatively better performance. But the Sun virtual box supports only one primary hard disk on the management console so no matter how many virtual machine created it will be linked to only one bootable primary virtual hard disk. Can’t ask for better limitation.
Once the Virtual machine is setup repeat the above method to create different virtual machine easily or else copy paste the machine incase required. Thus if there is a test setup of interacting and highly configured machines. The above process can easily create the required backup and create a virtual lab in less effort with high preserving. No information loss, no application configuration changed but all made virtual.
Now let’s look at to the Virtual players and their feature which can help in deciding which virtual machine player and management application can be used to maintain the virtualized setups.
VMware Player and Workstation :-
VMware applications and tools have been a disappointment for me when it comes to the performance of the virtual machines. The virtual machines were running slow on the VMware player, secondly VMware workstation was paid and I had to let if off. VMware installs lot information and tools on the host PC to give the virtualization feel, like separate virtual network adapter and device installations but none were able to give good network performance to the virtual machines, I had created. VMware is still a good choice when considered for ease of use and multiple virtual machine management.
Microsoft Virtual PC 2007:-
Sun Virtual Box:-
When it comes to the performance Sun Virtual box should be scored higher compared to it big competitors mentioned above. The Virtual machine performs well over network by impressive virtualization of the network adapter. The virtual resources management of Sun Virtual Box manages Microsoft Windows operating system better than the Microsoft Virtual PC 2007. But after all the goods, sun virtual Box allows only one primary virtual hard disk, so no matter how many virtual machine created they would be using the same virtual HD to boot i.e. better run one machine at a time. To make the situation worse to switch the machine u need to reload it or reconfigure it on the management console, why would someone should take so much of pain, when virtualization should make things easy ?
When acceptance is solution: -
I need ease of Microsoft Virtual PC, performance of Sun Virtual Box and features of VMware. Currently I am considering Microsoft Virtual PC overall for its advantages minus performance hiccups.





