虚拟机迁移三种情况(虚拟机迁移时的规则)

1. Copy the virtual machine files on the VMware host to the VMM library 1. Open vSphereClient and connect to the vCenter server
2. On the home page, click "Data Storage and Data Storage Clusters"
3. Select the data storage, right-click "Browse Data Storage"
4. Select a virtual machine, here we choose windows8, Then click the download button on the menu bar to download to the local area
5. Select a local path, and click "Yes" in the pop-up warning dialog box
6. As can be seen in the figure below, the data is being downloaded to Local
7. After the data download is completed, we copy the data to the VM library
2. Users need to use the VMM2012SP1 console to convert the VMware virtual machine to Hyper-V 1. Log in to the VMM console and click "VM and Services", click the "Create Virtual Machine" drop-down triangle in the menu bar, and click "Convert Virtual Machine"
2. The Convert Virtual Machine Wizard pops up. On the select source page, click "Browse"
3. Select the Windows virtual machine we saved in the VMM library and click "OK"
4. On the Specify Virtual Machine Identification page, specify the virtual machine name, and then click "Next"
5. In the VM Configuration page, specify the basic configuration of the new computer, and click "Next"
6. On the host selection page, select a suitable host to host the VMware virtual machine to be converted based on the rating score, and then click "Next"
7. On the Select Path page, select the path used by the target Hyper-v host to store the VM, and then click "Next". Then on the network page, configure the network for the VM, and then click "Next"
8. On the Add Properties page, configure VM-related properties, and then click "Next"
9. On the summary page, click "Create" and wait for the virtual-to-virtual conversion job to complete
10. After completion, you can Start the newly converted virtual machine in the VMM console
Using this method can quickly and easily migrate the VMware virtual machine to the Hyper-v platform seamlessly. Single users need to pay attention to it in actual operation (this method requires the environment It also has management platforms such as SCVMM and Vcenterserver, and the guest operating system must uninstall VMwareTools and turn it off).

Virtual-to-Virtual migration
V2V migration is to move operating systems and data between virtual machines, taking care of the host level Differences and handling of different virtual hardware. A virtual machine is migrated from the VMM on one physical machine to the VMM on another physical machine. The two VMM types can be the same or different. For example, VMware migrates to KVM, and KVM migrates to KVM. There are several ways to move a virtual machine from one VMHost system to another.
V2V offline migration
Offline migration (offlinemigration): also called regular migration and static migration. The virtual machine is paused before migration. If the storage is shared, only the system state is copied to the destination host. Finally, the virtual machine state is rebuilt on the destination host and execution resumes. If local storage is used, the virtual machine image and state need to be copied to the destination host at the same time. The migration process to this method requires explicitly stopping the virtual machine. From the user's perspective, there is a clear period of time when the service is unavailable. This migration method is simple and easy to implement and is suitable for situations where service availability is not strict.
V2V online migration
Online migration (onlinemigration): also called live migration (livemigration). It refers to migrating virtual machines between different physical hosts while ensuring the normal operation of services on the virtual machines. The logical steps are almost identical to offline migration. The difference is that in order to ensure the availability of virtual machine services during the migration process, the migration process only has a very short downtime. In the early stage of migration, the service is running on the source host. When the migration reaches a certain stage, the destination host already has the necessary resources to run the system. After a very short switch, the source host transfers control to the destination host, and the service is on the destination host. Continue running. As for the service itself, since the switching time is very short, users will not feel the interruption of service, so the migration process is transparent to users. Online migration is suitable for scenarios that require high service availability.
The current mainstream online migration tools require the use of centralized shared external memory devices such as SAN (storage area network) and NAS (network-attached storage) between physical machines. Therefore, only the operating system memory execution needs to be considered during migration. State migration to achieve better migration performance.
In addition, in some situations where shared storage is not used, storage block online migration technology can be used to implement V2V virtual machine online migration. Compared with online migration based on shared storage, online migration of data blocks requires the virtual machine disk image and system memory status to be migrated at the same time, which compromises migration performance. But he made it easier to use points