James In today's LinuxWorld session by Simon Crosby, CTO of XenSource, and shepherd of the Xen open source project made the contention that the open source community is holding itself back by not ensuring compatibility between Xen, KVM and the other open source virtualization efforts. He's right to a degree in that standards for foundation functions would allow the greater community to enhance virtualization for all, but should we honestly hold out hope of this happening? As is always the case in the open source world, the crowd goes where the excitement is and popularity wins. It would be a waste of the community's efforts to try and drive standardization where it isn't wanted and to try and ensure compatibility between competing implementations when everyone expects a winner to emerge.Xensource_toplogo

Enterprise customers want things they can count on, especially if they are pitched for use in production. The fickleness of the open source community runs counter to this desire which keeps open source technologies in the fringe until a commercial entity hardens them and wraps them in professional support offerings. This commercialization collects the interest of the community that wants to make a profit and, voila, the winner emerges. It's not the community that holds back open source projects its failure to bridge the desires of the commercial customers and ISVs and the community enthusiasts – the key to this is collective advancement of the chosen project.

XenSource shouldn't worry about whether they're compatible with KVM. They should worry about how quickly Xen matures. The rest is just noise in the system.

By James Staten

Check out James’ research