How to implement Hyper-V virtual machines migrating between processors in different architectures

For the traditional non-virtualization environment of IT technology, we from the computer room hardware server to the user's information, can be divided vertically into the following levels.

In this structure, we all know that if you simply migrate the operating system and the upper level to different hardware platforms, there will be many unpredictable compatibility issues.

With the development of hardware computing and the maturation of virtualization technology, more and more enterprises are deploying virtualized environment. In the virtualized environment of Hyper-V, we can understand the traditional hierarchy as follows:

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/virtualization/

Under such an architecture, there is a question of whether virtual hardware in the Hyper-V layer is the same between hardware processors in different architectures. For example, our customers may need to use several different architectures of servers to build Hyper-V virtualization clusters, at which point the problem must be addressed.

By default, virtual processors are not able to implement this migration because they differ in the instruction set of the physical processor. The solution given by Hyper-V is at the virtual machine level and can be set to backward compatibility, which, of course, sacrifices the advantage of a better architecture processor. Furthermore, it is not possible to migrate between Intel and AMD processors.

The specific configuration scenario is as follows: In the virtual machine settings, select the processor settings, find the following figure, and check the selection:

This article from the "Ghost Emperor" blog, please be sure to retain this source http://ghostlan.blog.51cto.com/5413429/1299083