There’s been a lot of interesting product wars over the years: WordPerfect vs. Word, 1-2-3 vs. Excel, Harvard Presentation Manager vs. PowerPoint, Novell vs. Windows NT, Netscape vs. Internet Explorer, Palm OS vs. Windows Mobile, and the list goes on and on.
One of the current product battles taking shape is in server virtualization. And, like many past product confrontations, Microsoft’s Hyper-V is the late-to-the-game underdog. VMware’s ESX and Vmotion are the clear market and technology leaders right now. And, there are other viable virtualization hypervisor alternatives including Sun xVM, KVM, and Parallels Server.
However, it doesn’t matter how good the underlying hypervisor is if you don’t have any Guest OS to install on it because of licensing problems. It is an easy decision to use CentOS, Fedora, Ubuntu, or any of the Debian derivatives because there is licensing issue I can think of with those Linux distros. This is important both to end-users and virtual appliance builders. And, it gives the LAMP stack an advantage over WAMP, WIMP, and WISP stacks for the same two groups.
Licensing issues are not limited to the Windows operating system itself. Virtualization has moved beyond simply virtualizing server stacks. In the past year we’ve see a huge movement towards virtualizing desktops and even individual applications. Both Microsoft and VMware have moved aggressively in this space buying technology to fill the gaps between virtualization tiers. But, still it is complicated, from a licensing point of view, to decide when you are able virtualize Windows Vista, Word, Exchange Server, and other licensed Microsoft products. Commercial Open Source products can create similar licensing issues. However, there is usually the option to use the lesser supported Community Editions of these kinds of products (MySQL, for example) for testing and development, for example.
All software firms with commercially licensed products need to resolve how to allow their customers to run their products in virtual environments.