nerdexam
Broadcom-VMware

2V0-622D · Question #283

When attempting to migrate a virtual machine to another host in the same cluster, the error message, "Select a valid compute resource" returns. What could cause this error?

The correct answer is B. Both hosts are not sharing the same datastore.. The vMotion error 'Select a valid compute resource' occurs when the destination host cannot access the VM's current datastore, making it an invalid migration target.

Section 8 – Deploy and Administer VMware Virtual Machines

Question

When attempting to migrate a virtual machine to another host in the same cluster, the error message, "Select a valid compute resource" returns. What could cause this error?

Options

  • AVMware Tools is not installed.
  • BBoth hosts are not sharing the same datastore.
  • CVirtual machine has an ISO attached.
  • DBoth hosts run different versions of ESXi.

How the community answered

(56 responses)
  • A
    4% (2)
  • B
    79% (44)
  • C
    5% (3)
  • D
    13% (7)

Why each option

The vMotion error 'Select a valid compute resource' occurs when the destination host cannot access the VM's current datastore, making it an invalid migration target.

AVMware Tools is not installed.

VMware Tools affects in-guest performance features and quiescing but is not a vMotion prerequisite and would not trigger a compute resource validation error.

BBoth hosts are not sharing the same datastore.Correct

vMotion requires that both the source and destination hosts share access to the same datastore so the VM's disk files remain accessible during migration. If the destination host cannot see the datastore, vCenter marks it as an invalid compute resource and blocks the migration.

CVirtual machine has an ISO attached.

An ISO attached from a local datastore can block vMotion, but the resulting error identifies the CD/DVD device as the problem, not an invalid compute resource.

DBoth hosts run different versions of ESXi.

Mismatched ESXi versions can cause CPU compatibility errors enforced by EVC settings, but those produce a CPU incompatibility message rather than the compute resource error described.

Concept tested: vMotion shared datastore requirement for live migration

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-D19EA1CB-5222-49F9-A002-4F8692B92D63.html

Topics

#vMotion#shared datastore#migration error#compute resource

Community Discussion

No community discussion yet for this question.

Full 2V0-622D Practice