If you are “hot” converting a live VM, then additional time will be needed to synchronize any changes that have occurred during the time the conversion was being done. Additionally, VM image files can be very large, and take a significant amount of time to convert. To move to a new hypervisor platform the VM’s files need to be converted from their existing format to a format usable by the new hypervisor – a “virtual to virtual” or V2V conversion. ![]() However, moving to a different hypervisor is a more complex proposition. Moving a VM to a different host using the same hypervisor is accomplished by pointing the new host to the VM’s files. Some of the files hold an image of the VM, while other files provide details about how the VM should be implemented. Virtual machines (VM) are made up of a set of files in a format specific to the hypervisor on which they are running. In this post we’ll focus on another important step: migrating VMs from one platform to another. ![]() ![]() One step in migrating between VMware and Hyper-V is to reproduce management features, as we discussed in our post on converting from VMware High Availability to Hyper-V’s Failover Clustering.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |