A new vApp was built and tested in the corporate headquarters datacenter running vSphere 6.x. What condition would explain why the virtual machine is failing to boot in an offsite datacenter running on vSphere 5.5?

Question

Accepted Answer

A. The virtual machine was built with the default hardware version. vSphere 6.x assigns a default virtual hardware version of 11 (VMX-11) or higher to new VMs, while vSphere 5.5 hosts only support up to virtual hardware version 10 (VMX-10). When that VM is migrated to the 5.5 datacenter, the ESXi 5.5 host cannot interpret the newer hardware version and refuses to power it on. The fix is to upgrade the offsite hosts or downgrade the VM hardware version before migration.

Answer

B. The VMFS 5 datastore is not compatible with virtual machines configured with vSphere 6.x. VMFS 5 is a datastore format version and is compatible across multiple vSphere host versions; it does not restrict which virtual hardware versions can be stored or accessed.

Answer

C. A DRS 5.5 cluster cannot run virtual machines configured with vSphere 6.x. DRS is a cluster resource management feature and does not impose restrictions based on VM hardware version compatibility.

Answer

D. The VMDK file is locked. A locked VMDK produces a file-lock error during power-on, not a hardware version incompatibility failure, and would not be caused by a version difference between datacenters.

A new vApp was built and tested in the corporate headquarters datacenter running vSphere 6.x. What condition would explain why the virtual machine is failing to boot in an offsite datacenter running…

Question

Options

How the community answered

Why each option

Topics

Community Discussion