Andreas, I am using vSphere 5. Error: The target host does not support the virtual machine's current hardware requirements. See KB article To your point it may be related to vCenter 5. Yep, on 5. Have you ever been bugged by a vMotion Compatibility check error that you couldn't really explain e. Because - like no other technology - it demonstrates the superiority of virtual machines over physical servers, their independence from the underlying physical hardware.
It enables machine mobility and theoretically eternal uptime. But the hardware independence is not complete: Unlike other devices CPUs are not emulated by the hypervisor, but passed through to the VM, utilizing hardware virtualization features that are built into the processor - in partly vendor specific ways. As a consequence vMotion does only work between similar CPUs of the same vendor - by default.
VMware vCenter the component that controls vMotion operations puts a lot of effort in ensuring vMotion compatibility between source and target hosts whenever a Live Migration task is about to be performed be it manually or automatically through DRS.
And by default it will prevent a vMotion task from being started if it finds CPUs to be incompatible. How to relax and disable vMotion Compatibility checks Although it is not recommended sometimes it is desirable to relax or completely disable the vMotion compatibility checks.
This is possible by configuring certain advanced vCenter settings. These are set through the legacy vSphere Client for vSphere versions prior 5. Adding the key config. CpuCompatibleWithHost with value false will completely disable all compatibility checks. This is the brute force method, and I would really not recommend doing this, because this will also suppress any warnings to be shown. CpuCompatibleMonitorSupport with value false will only disable checking the VMM Virtual Machine Monitor on the source and target hosts for supported CPU features preventing any "product version does not support features" error messages.
Here is the VMware link to do the custom masking. One thing i did notice is that some machines actually played nicer when being moved from Intel to AMD. This was the most frustrating on my Horizon View Connection Server. Your email address will not be published. Notify me of follow-up comments by email. Notify me of new posts by email. During a Cold Migration , the virtual machine on the original host is shut down in a controlled manner first. Then it is started on the new host.
This results in a short interruption of the virtual machine operation. For most applications, it does not matter if a VM created on an Intel-based host runs on an AMD-based host after a cold migration or vice versa. The prerequisite here is that the respective application software supports the functions of both manufacturers. In his spare time he enjoys playing the piano and training for a good result at the annual Linz marathon relay.
Views View View source History. Personal tools Create account Log in. From Thomas-Krenn-Wiki.
0コメント