Skip to content

June 28, 2012

Hyper-V Live migration

使用多台机器做Hyper-v Live migration.若我的硬设备不同如下,Guest 機器在这三台机器(Failover Cluster)移转会不会有問題,有哪些须特别注意

HP 380 G5(Intel CPU)、HP 380 G6(Intel CPU)、HP 785 G6(AMD CPU)

 

回答:关于您的问题:

Intel和Amd cpu,是绝对不能一起做cluster的。而G5 G6,只要Intel cpu类型差不多,那就没问题了。

最多在live migration时,选上“Migrate to a physical computer with a different processor version”

Hyper-V Live Migration Setting

Hyper-V虚拟机实时迁移设置

Lamb Shu 

 

Hyper-V实时迁移的相关描述,如下:

How Live Migration Works

Live migration takes place between two Hyper-V hosts. Essentially, the VM memory is copied between Hyper-V hosts. After the memory is copied, the VM on the new host can access its virtual hard disk (VHD) files and continue to run. Both hosts access shared storage where the VM’s VHD files are stored. When you initiate a live migration, which Figure 1 shows, the following steps occur:

  1.       A new VM configuration file is created on the target server.
  2.       The source VM’s initial memory state is copied to the target.
  3.       Changed memory pages on the source VM are tagged and copied to the target.
  4.       This process continues until the number of changed pages is small.
  5.       The VM is paused on the source node.
  6.       The final memory state is copied from the source VM to the target.
  7.       The VM is resumed on the target.
  8.       An Address Resolution Protocol (ARP) is issued to update the network routing tables.

Requirements for Live Migration

On the hardware side, you need two x64 systems with compatible processors. It’s best if the host processors are identical, though it’s not required. However, they do need to be from the same processor manufacturer and family—you can’t perform a live migration when one host has an AMD processor and the other host has an Intel processor. Learn more about Hyper-V processor compatibility in the Microsoft white paper “Virtual Machine Processor Compatibility Mode.”

      In addition, each of the servers should be equipped with at least three NIC cards, running at 1GHz: one for external network connections, one for iSCSI storage connectivity, and one for node management. Ideally, you’d have another NIC dedicated to the live migration, but the live migration can also occur over the external network connection—it will just be a little slower. It’s important to note that if you’re implementing a server consolidation environment, you will want additional NICs for the network traffic of the VMs.

      On the software side, all the nodes that take part in live migration must have Server 2008 R2 x64 installed. This can be the Standard, Enterprise, or Datacenter editions. Live migration is also supported by the Hyper-V Server 2008 R2 product. In addition, the Hyper-V role and the Failover Cluster feature must be installed on all servers participating in live migration.

      You also need shared storage, which can be either an iSCSI SAN or a Fibre Channel SAN. In this example, I used an iSCSI SAN. Be aware that the iSCSI SAN must support the iSCSI-3 specifications, which includes the ability to create persistent reservations, something that live migration requires. Some open-source iSCSI targets such as OpenFiler don’t have that support at this time. If you’re looking to try this for a local test and don’t want to buy an expensive SAN, you might want to check out the free StarWind Server product at www.starwind.com. 

 

Hyper-V Live migration的相关文章请参考

hyper-v是什么 

hyper-v虚拟化技术 

更多Hyper-V的文章请猛击 http://adirectory.blog.com/tag/hyper-v/ 

—gnaw0725

    Leave a Reply