Unable to move VMs between hosts after patching

ppinfrageek 121 Reputation points
2024-05-28T15:34:28.7466667+00:00

Our InfoSec team patched our three-node cluster and now the VMs are failing to migrate to the first node. The message is as follows:

"Live migration of 'Virtual Machine pvx4050' failed.

Virtual machine migration operation for 'pvx4050' failed at migration destination 'CL01-001'. (Virtual machine ID DA2107DB-7742-4079-8766-CB3F029B4DDB)

The processor settings for virtual machine 'pvx4050' are not compatible with physical computer 'CL01-001'. To migrate this virtual machine, you must first shut it down. After shutdown, you can migrate this virtual machine or export it and then import it on the destination physical computer with the correct processor settings. (Virtual machine ID DA2107DB-7742-4079-8766-CB3F029B4DDB)"

Even if I tick the box for "Migrate to a physical computer with a different processor version" under Settings / Processor / Compatibility - I still can't migrate VMs to the first host and the host hardware is identical BTW.

Any idea what may be causing this? THe VMs have no checkpoints.

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,613 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian Xue (Shanghai Wicresoft Co., Ltd.) 33,301 Reputation points Microsoft Vendor
    2024-05-29T04:21:45.35+00:00

    Hi ppinfrageek,

    Hope you're doing well.

    1. Ensure that all virtual machines are stored in a CSV.
    2. Test "Move" by storing the virtual machine on a local path, and the virtual machine successfully moved from the source to the destination.
    3. Ensure that the patch levels of the source and destination servers are consistent and up to date.
    4. Try to disable 3rd party antivirus software.
    5. Checked the CPU configuration of the source and destination servers to confirm all CPUs have the same configuration.
    6. Due to the resource limitation of forum, we cannot collect more logs for further investigate. We suggest you to open a Microsoft ticket.

    Best Regards,

    Ian Xue

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments