Cross-vCenter vMotion of a VM with vTPM fails with "Select a valid destination compute resource"
search cancel

Cross-vCenter vMotion of a VM with vTPM fails with "Select a valid destination compute resource"

book

Article ID: 424420

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When attempting to perform a Cross-vCenter vMotion for a virtual machine (VM) equipped with a vTPM, you may encounter the following message in the "Select a compute resource" dialog, preventing the operation from proceeding:
    Select a valid destination compute resource.
  • Upon selecting a cluster or ESXi host in the same dialog, the "Compatibility" pane displays the following error:
    A general runtime error occurred. Key provider ######## not found.
  • In this scenario, the source and destination vCenter Servers are configured with different Native Key Providers.

Environment

vSphere 8.0

Cause

When migrating a VM with vTPM between vCenter Server instances, the Native Key Provider from the source vCenter Server must be restored onto the destination vCenter Server instance. 

Resolution

To resolve this issue, follow the steps below:

  1. Back up the Native Key Provider from the source vCenter Server. For detailed steps, refer to: 
    Back up a vSphere Native Key Provider 
  2. Restore the backed-up Native Key Provider to the destination vCenter Server. For detailed steps, refer to: 
    Restore a vSphere Native Key Provider Using the vSphere Client
  3. Verify that the Key IDs match between the source and destination vCenter Servers for the newly restored Native Key Provider.
    To verify the Key IDs, follow these steps:
     - In the vSphere Client, select the vCenter Server.
     - Navigate to Configure > Security > Key Providers.
     - Select the relevant Key Provider to view and compare the Key ID.
  4. Retry the Cross-vCenter vMotion.
    Note:
    Post-Migration Recommendation: If you plan to keep the VM running on the destination vCenter Server permanently, consider re-keying the virtual machine after migration to ensure consistency within the new environment.
    For instructions on re-keying, see: 
    Rekey an Encrypted Virtual Machine Using the vSphere Client

Additional Information

What Is Encrypted vSphere vMotion