The Kensho Project tools are slated to become available in September and will focus on enabling workloads based on an emerging standard called Open Virtual Format. When built with OVF tools, a virtual workload can run under any hypervisor.
![]() | ![]() |
![]() Crosby's gone interoperable | |
![]() |
The Citrix tools will convert virtualized files into Microsoft's Virtual Hard Disk format, which is used for formatting a virtual machine as a set of files stored to disk. The tools capture application and virtual machine configuration data in an XML schema set by the Distributed Management Task Force, the standards body that ratified OVF, says Simon Crosby, Citrix's virtualization CTO and XenSource's founder.
VMware actually proposed OVF as a standard. VMware saw rivals Microsoft and Citrix align around Microsoft's VHD. While VMware's VMHD is the industry's dominant format, the company risked being typecast as a lock-in risk, or even a backwater, if VHD became more widespread. So VMware proposed OVF in February 2007 as a standard and embraced building virtual appliances so that each workload had its own VM, operating system, and applications. XenSource--the open source company built around the open source Xen hypervisor--agreed to co-author the draft standard, and other vendors, including Dell, Hewlett-Packard, IBM, and Microsoft, joined in. Citrix bought XenSource in August 2007.
InformationWeek Analytics Report free for a limited time.
In announcing its Kensho tools ("kensho" means "enlightened experience" in Japanese), Crosby emphasized Citrix's commitment to interoperability. With VMware dominating virtualization, Citrix has every reason to make it easier for managers to move workloads from VMware to XenServer. In that sense, Kensho means an off-ramp from a competitor's product.
But if it lives up to its advance billing, OVF could just as easily be on-ramp to VMware's Virtual Infrastructure 3, its platform for managing VMs. The whole goal is to make moving virtual workloads a two-way street.