An administrator notices that one virtual machine is in an orphaned state.
What are two reasons that a virtual machine can appear as orphaned? (Choose two.)
A.
A VMware High Availability host failure has occurred.
B.
The virtual machine was unregistered directly on the host.
C.
The ESXi host is disconnected.
D.
The user does not have privilege to access the virtual machine.
Explanation:
Explanation/Reference:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003742
A and B are correct
http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-BFD8C9BC-30FB-4A92-AFEC-2FC9FF387920.html
I would say A and C which is also confirmed here:
“Virtual Machines show as invalid or orphaned after the connection is lost between the vCenter Server and the host where the virtual machine resides”
From:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003742
And from personal experience where for some reason the ESX host gets disconnected, the VM’s that reside on that host are listed as disconnected.
AB
As EP says, when ESXi host is disconnected VM shows as disconnected, not orphaned
B definitely true
A: I dont like A, but I dont see anything better either. Above docs say that a failed HA failover will leave the VM in orphaned state, they do not say that all HA failovers (successful ones too) leave them orphaned…
AB
After a vMotion or VMware DRS migration
After a VMware HA host failure occurs, or after the ESX host comes out of maintenance mode
A virtual machine is deleted outside of vCenter Server
vCenter Server is restarted while a migration is in progress
Too many virtual machines are scheduled to be relocated at the same time
Attempting to delete virtual machines when an ESX/ESXi host local disk (particularly the root partition) has become full
Rebooting the host within 1 hour of moving or powering on virtual machines
A .vmx file contains special characters or incomplete line item entries
Reload all invalid virtual machines on a single host at one time
vCenter database is full