Virtual Machine not Compatible with any Host

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• When you try to power on VM you get the following error: "Virtual Machine not Compatible with any Host"
• In the hostd.log file, you see entries similar to:

  • 
    Cannot open the disk '/vmfs/volumes/5b380d0a-########-####-########4610/VM1/VM1.vmdk' or one of the snapshot disks it depends on.
    -->
    [YYYY-MM-DDTHH:MM:SS] info hostd[2101869] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=########] Event 263 : Error message on HOST on localhost.localdomain in ha-datacenter: Cannot open the disk '/vmfs/volumes/5b380d0a-########-####-########4610/VM/VMNAME.vmdk' or one of the snapshot disks it depends on.
    [YYYY-MM-DDTHH:MM:SS] info hostd[2101875] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5b380d0a-########-####-########4610/VM1/VM1.vmx opID=########] Answered question 20586
    [YYYY-MM-DDTHH:MM:SS] verbose hostd[2101875] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5b380d0a-########-####-########4610/VM1/VM1.vmx opID=########] Handling vmx message 20587: Plugin loading error
    --> Cannot open the disk '/vmfs/volumes/5b380d0a-########-####-########4610/VM1/VM1_3.vmdk' or one of the snapshot disks it depends on.
    [YYYY-MM-DDTHH:MM:SS] info hostd[2101875] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=########] Event 264 : Error message on HOST on localhost.localdomain in ha-datacenter: Cannot open the disk '/vmfs/volumes/5b380d0a-########-####-########4610/VM/VMNAME.vmdk' or one of the snapshot disks it depends on.

• In the vmware.log file of the VM, you see entries similar to:

  • In the vmware.log file of the VM, you see entries similar to:
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: Destroying virtual dev for scsi0:0 vscsi=114010
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: VMMon_VSCSIStopVports: No such target on adapter
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: Destroying virtual dev for scsi0:1 vscsi=114011
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: VMMon_VSCSIStopVports: No such target on adapter
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: Closing disk 'scsi0:0'
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: SVMotion_DiskCloseCB: Closing disks in svmPhase 0. Not destroying mirror node.
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: DISKLIB-CBT   : Shutting down change tracking for untracked fid 714885865.
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: DISKLIB-CBT   : Successfully disconnected CBT node.
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: DISKLIB-VMFS  : "/vmfs/volumes/5b380d0a-########-####-########4610/VM2/VM2-000002-se
    sparse.vmdk" : closed.
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: DISKLIB-VMFS  : "/vmfs/volumes/5b380d0a-########-####-########4610/VM2/VM2-000001-se
    sparse.vmdk" : closed.
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: DISKLIB-VMFS  : "/vmfs/volumes/5b380d0a-########-####-########4610/VM2/VM2-flat.vmdk
    " : closed.
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: Checkpoint_Unstun: vm stopped for 38261 us
    [YYYY-MM-DDTHH:MM:SS] vmx| I125: VigorTransport_ServerSendResponse opID=######## seq=4557577: Completed DiskEarlyDevice request.
    [YYYY-MM-DDTHH:MM:SS] vcpu-0| I125: LSI:Rescan requested for scsi0...
    [YYYY-MM-DDTHH:MM:SS] vmx| I125: VigorTransportProcessClientPayload: opID=######## seq=4557584: Receiving HotPlugManager.EndBatch request.
    [YYYY-MM-DDTHH:MM:SS] vmx| I125: VigorTransport_ServerSendResponse opID=######## seq=4557584: Completed HotPlugManager request.
    [YYYY-MM-DDTHH:MM:SS] vcpu-12| I125: HBACommon: First write on scsi0:4.fileName='/vmfs/volumes/649c174e-########-####-####
    ####a32c/VM3/VM3.vmdk'
    [YYYY-MM-DDTHH:MM:SS] vcpu-12| I125: DDB: "longContentID" = "49cc880537a223a4f115ea9a37ca75e2" (was "c84c17ef6902d4e7bbc8f
    590fffffffe")
    [YYYY-MM-DDTHH:MM:SS] vcpu-12| I125: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0xfffffffe, new=0x37ca75e2 (49cc880537a
    223a4f115ea9a37ca75e2)
    [YYYY-MM-DDTHH:MM:SS] svga| I125: MKSScreenShotMgr: Taking a screenshot
    [YYYY-MM-DDTHH:MM:SS] vmx| I125: TOOLS autoupgrade protocol version 0
    [YYYY-MM-DDTHH:MM:SS] vcpu-12| I125: GuestRpc: Reinitializing Channel 0(toolbox)

Environment

VMware vSphere 6.7.x
VMware vSphere 7.0.x

Cause

• This fault occurs when DRS cannot find a host that can run the virtual machine. This might occur, for example, if no host can satisfy the virtual machine's CPU or memory resource needs or if no host currently has network or storage access needed by the virtual machine.
• Another reason: if VM was copied or moved.

Resolution

• To address this problem, provide a host that can meet the virtual machine's requirements ( Resources, HW Compatibility, .. ).
• On other scenario ( if VM was copied or moved ): you might need to go to host web client and answer question of ( moved it or copied it ) if it doesn't appear in vCenter web client.
• You might try to disable DRS and admission control for testing.

Workaround:

• Create New VMs.
• Recreating the VMDKs using KB : Recreating a missing VMware virtual machine disk descriptor file (.vmdk)
• Proceed with attaching the new VMDKs to the VMs then power on the VMs.

Additional Information

Failed to power on virtual machine

Refer:
Virtual Machine not Compatible with any Host
vSphere Resource Management

Impact/Risks:
Impact: cannot power on VM from vSphere client but you can using cli commands.
Impact: cannot power on VM from vSphere client and from the SSH as well.