A. This question refers to situations such as if you have a guest running on VMware ESX and you perform a virtual to virtual (V2V) migration to Hyper-V. ESX has its own virtual additions, which install drivers and services into the guest OS. When you migrate to Hyper-V, Hyper-V adds its own integration services, assuming the OS doesn't already have the integration services built in.
It wouldn't be ideal to leave the additions from the old hypervisor in the guest, and so as part of the V2V migration the old additions should be removed as soon as possible. Removing them will help you avoid complications.
Related Reading:- Q. How can I perform a virtual to virtual (V2V) migration with System Center Virtual Machine Manager (SCVMM) 2008?
- 10 Steps for Physical to Virtual OS Migration
- Q. What OSs does System Center Virtual Machine Manager (SCVMM) 2008 support as sources for physical to virtual (P2V) migration?
- Q. What is System Center Virtual Machine Manager (SCVMM) 2008?
Check out hundreds more useful Q&As like this in John Savill's FAQ for Windows. Also, watch instructional videos made by John at ITTV.net.
0 comments
Hide comments
