Article ID: 969726 - View products that this article applies to.
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
When you try to migrate a Virtual Machine (VM) from one Host to another from the SCVMM 2008 Console it may fail with the following error:
"Unable to migrate the virtual machine <virtual Machine Name> because the processor is not compatible with the host <Host Name>"
"Unable to migrate the virtual machine <name> because the processor is not compatible with the host <host>."
This error appears in the Migrate Virtual Machine Wizard in the "Rating Explanation" section, where the rating was zero.
The target host may also show the following status:
Overall Status: OK
Connection status: Responding
Agent status: Responding
Agent version: Up-to-date
Virtualization service status: Running
Virtualization service version: Up-to-date
The box next to "This host is available for placement" is checked.
When migrating a Virtual Machine which has a saved state, SCVMM uses built-in checks to determine whether a saved state VM can be migrated between hosts or deployed from a library to a host. If these checks fail then we get the error message. A few things we compare include:
· Manufacturer (eg. Intel vs AMD)
· Processor architecture (x86 vs x64)
· Virtual Server version (SP1 vs R2 SP1)
· Family of the processor
If any of these values are different between the two hosts then that host is not valid to do a saved state migration.
As a workaround, you can delete the Snapshots/Checkpoints and shutdown the VM. Once you do this you should be able to migrate it from one host to another.
Note: In VMM 2008 R2, you can set the Allow migration to a virtual machine host with a different processor property to allow a virtual machine to run on a host that has a different processor version than the host on which the virtual machine was created. The virtual machine must be stopped to set this property.
Setting the Allow migration to a virtual machine host with a different processor property allows for greater flexibility in live or saved-state migrations; however, it reduces the functionality of the virtual machine’s processor. So you should use this only when necessary, such as to facilitate live migration between clustered hosts that have different processor versions.Setting the Allow migration to a virtual machine host with a different processor property allows for greater flexibility in live or saved-state migrations; however, it reduces the functionality of the virtual machine’s processor. So you should use this only when necessary, such as to facilitate live migration between clustered hosts that have different processor versions.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.