When moving VMs from RHEV, KVM, Hyper-V, and VMware, which many are doing today, OVF makes sense as a starting point, however, OVF is very ineffecient if the given VMs already have virtual disks in the correct location. For example, moving VMs from VMware to KVM, and from KVM to VMware, since KVM supports VMDK as does VMware, and both could and can access the same datastore/NFS mount point, the encode/decode of the virtual machine disks in OVF is not needed, just use a reference path to the VM disks, not the actual data. So the question is, When will OVF support disk reference paths and not embed disk data into mgiration file? Interesting feature no?
↧