OVF isn’t the nirvana that it’s reported to be, it’s missing the most important detail – the disk image. While it does a great job of describing metadata the disk image is poorly defined. Vendors can use their own disk format – eg. Driver Converter Stick Ps2 Roms. Vmdk, vhd, qcow, raw, etc so unless your hypervisor supports them all (and to-date no one does) then you have to convert the image before you import. Then there’s the issue of drivers, what drivers and configuration do you load in the VM? VMware uses scsi emulation or their own PV driver for disk, Xen uses IDE or their own drivers, KVM uses. So even if you can read the image you have to swap out the drivers that were installed, or make sure that all OVFs include VMware, Xen, Microsoft, KVM, drivers and config files.

For a homogeneous hypervisor world OVF is fine, but in reality it’s fundamentally flawed •.

You can deploy the OVA file on vSphere 5.x for use during development or for production environments. In addition, can deploy the OVA file on VMware Workstation 9.x, VMware Fusion 5.x, or VMware Player 5. Easy Mail Recovery 2.0 Serial. x fur use during development. Right-click an inventory object that is a valid. Download and run the OVF Tool setup program on the workstation or server running VMware (see Resources). Click 'Next' to accept the license agreement and install the OVF Tool. Click the 'Start' button, type 'cmd' in the search field and press 'Enter' to open the command prompt in Windows.