Why XenSource and not VMware?
A common question we get from analysts and something that continues to come up in discussions (see Brian Madden’s blog) is why we developed everRun VM for XenSource and not VMware. One of the biggest obstacles in developing a version of our software for protecting virtual environments was making a strategic decision on which hypervisor platform to develop for initially. Some of the key factors that weighed in on our decision were:
- Virtualization platform market share
- Robustness of the virtualization platform
- Performance of the virtualization platform
- Openness of the architecture
- Virtualization vendor’s approach to partnerships
- Compatibility with future Microsoft virtualization platforms
Although VMware was the clear market leader, for most of the criteria, XenSource (now Citrix Virtualization and Management Division) was a much better fit. To acheive the superior availability that everRun VM uniquely provides, it had to be tightly integrated with the hypervisor, the openness of the architecture was very important. And since our solution would be directed at virtualizing applications that weren’t being virtualized yet, in part due to concerns about their performance in virtual machines, the near “bare-metal” performance of XenServer was also a major advantage. XenSource’s philosophy of growing through an ecosystem of technology partners gave us the confidence that they would get the technical, management and marketing support required to achieve our time-to-market objectives. Finally, because of the company’s relationship with Microsoft and the planned interoperability between the XenServer platform and Microsoft’s Hyper-V, we are confident that developing for XenServer now would provide the shortest path to supporting Microsoft Hyper-V when it becomes available.
If you have any additional questions feel free to leave us a comment.





