Print 42 comment(s) - last by .. on Aug 22 at 12:41 PM

Windows 7's XP Mode is one example of how virtualization is becoming more useful to home users and business users alike.
Virtualization is a way of getting more out of the same hardware -- are you taking advantage of it

While virtualization is not without its share of detractions, its allure is great. After all, it promises to make compatibility and resource management woes -- two eternal computer problems -- things of the past. 

Imagine being freed from fears of software compatibility, and being able to reclaim your idle hardware for a purpose.  That's the premise behind virtualization.  While new users may still not have heard of virtualization or understand its benefits, the movement is growing and it may eventually become as ubiquitous a concept as the desktop operating system.

Virtualization is divided into two key categories -- application virtualization and platform virtualization.  The goal of application virtualization is to provide compatibility layers.  This could allow you to, say run an old Windows 3.1 program on a Linux operating system.  The open source project Wine is an example of this kind of virtualization.

The second category is platform virtualization -- bringing the whole OS onboard.  There's a variety of ways of accomplishing this with solutions available in both the desktop and server markets.  Some solutions have multiple kernels (a central component of the OS) running in parallel, with one for each virtual machine (full virtualization), while other schemes involve a single kernel managing multiple virtual servers (a server is the interface users use to interact with the OS -- how we perceive Windows) allowing them to all to run at once.  Windows 7's XP Mode is one example of such a scheme -- in Windows 7 a guest virtual machine for Windows XP runs on the system, which communicates through the host Windows 7 kernel.

Some platform virtualization implementations, such as XP Mode, use redirection of input to accomplish application virtualization via platform virtualization rather than a compatibility layer.  The experience is more seamless as the Windows are displayed inline without the need to physically switch to a virtual machine window and navigate through its own windows.

A final important aspect of virtualization is the cloud computing movement.  Though not all cloud computing involves virtualization, many cloud deployments involve sharing virtualized resources over a network.  Shared resources are nothing new, but by virtualizing them, it lowers overhead and ensures that resources are efficiently used.  Google, IBM, and Microsoft are just a few of the major names delving into this field.  An example of cloud computing that even novice users can appreciate is Microsoft Office 2010, which will be available as free web applications for home users.

Virtualization is a fast evolving field and it is not without its problems and obstacles.  One obstacle is cost.  While costs of virtualization are dropping (Windows virtual machines for home users come with copies of Windows 7 Professional at no extra cost), deploying such a solution at your business may require some up-front IT investment and hours.  In the long run it will save costs, but for cash-strapped businesses, this can be a deterrent to adoption, albeit one that will eventually be overcome.

Another more serious challenge is the increased likelihood of interruption of service.  By putting more services on a single set of hardware you raise the damage that could be caused by a power failure -- either at your location or from your system's power supply.  Furthermore, by running your hardware under larger workloads, you run the risk of a higher incidence of part failures.  Again, this is unproven territory as the field is still young, but logic dictates that hardware flexed to its full capacity will likely experience more failures than hardware that spends a significant amount of time in idle.  As the deployment of virtual machines is in the hands of system administrators, it’s up to them to make sure that they're not overburdening hardware.

A final challenge is security.  By placing multiple virtual machines on a single set of hardware, you run the risk of an escalated intrusion threat if an attacker can compromise the hypervisor layer -- the layer beneath the virtual machines.  Also in a guest/host setup (like Windows XP Mode) you run the risk of guest-to-host attacks, which can exploit vulnerabilities in legacy operating systems or applications.  Thankfully, such attacks have thus far been rare, but proof-of-concept exploits show the need for vigilance.  As always, diligent patching and careful system administration can protect your virtualized network against most threats.

With that said, how is virtualization impacting you?   How are you adopting virtualization at your home or business?  And, if you're not adopting virtualization, what's holding you back?

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

RE: One more issue to consider
By JonathanC3 on 7/24/2009 11:18:12 AM , Rating: 2
Sorry for the confusion. I should have stated the info about DC edition after. I know that it is not dependant on the virtualization technology used.

Since most SMB don't have Data Center edition, the difference of using Enterprise Edition with Hyper-V versus VMware is true. For the price of 1 license you get 1 physical + 4 VM.

RE: One more issue to consider
By Brovane on 7/24/2009 11:42:38 AM , Rating: 3
Understand. The sentance was confusing.

Also when you are trying to make your point about about MS virtualization maybe you shouldn't link to article's by MS. Of course MS is going to talk about how wonderful there virtualization product is over VMware.

I would agree that MS for the SMB is moving strong into this market. However at the Enterprise level they just didn't have the feature set that a Enterprise is looking for.

For example: Memory over-commit. In VMware I can give a VM 2GB of RAM but if the OS is using 1GB that is all VMware will give it. MS you give 2GB it will take all of 2GB. Also with VMware there is sharing of RAM between VM's. For example if I have 20 Server 2003 running on one physical host there is probably a lot of the same items loaded in RAM. VMware will share this between the OS's so this also cuts down on RAM. Basically VMware maximes your RAM usage.

I know that MS is playing catchup bigtime with VMware. I heard they finally got Live-Migrator working. VMware has had vMotion for years. I can move all my VM's around and I can move the VM files around on the SAN without any downtime.

The biggest complaint that I have always had about MS virtualization is the base OS is a MS OS. For VMware it is hardened Linux Kernel. I heard that Server 2008 Core load is supposeed to be a lot better. I will reserve judgement. Maybe give MS a couple of more years they will catch up to VMware at the Enterprise level.

RE: One more issue to consider
By JonathanC3 on 7/24/2009 11:58:33 AM , Rating: 2
The fact that you keep an open mind is impressive. Most people chose one side and stick to it no mather what. I've had the chance to work with VMware also and it is true that memory management is more developped on VMware. If you want to try MS solution, I suggest you wait for R2 RTM to be released.

"We basically took a look at this situation and said, this is bullshit." -- Newegg Chief Legal Officer Lee Cheng's take on patent troll Soverain

Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki