2V0-620 · Question #188
An administrator is attempting to power on a virtual machine, but is unable to do so. Which two reasons are probable causes of the failure? (Choose two.)
The correct answer is A. Storage access to the virtual machine swap file has been lost. B. One of the virtual machine VMDK files is locked.. A VM that cannot power on is most commonly caused by a locked VMDK file or inaccessible storage for the VM's swap file, both of which are required resources that vSphere must access during the power-on sequence.
Question
An administrator is attempting to power on a virtual machine, but is unable to do so. Which two reasons are probable causes of the failure? (Choose two.)
Options
- AStorage access to the virtual machine swap file has been lost.
- BOne of the virtual machine VMDK files is locked.
- CVirtual machine is running CentOS 7.0 64-bit.
- DVirtual machine has Hyper-Threading enabled.
How the community answered
(60 responses)- A75% (45)
- C7% (4)
- D18% (11)
Why each option
A VM that cannot power on is most commonly caused by a locked VMDK file or inaccessible storage for the VM's swap file, both of which are required resources that vSphere must access during the power-on sequence.
During power-on, vSphere must create or open the VM's memory swap file (.vswp) on a datastore; if the datastore is inaccessible due to lost storage connectivity, the operation cannot complete and the power-on fails.
If a VMDK is locked by another ESXi host or process (commonly occurring after an unclean VM shutdown or host failure), vSphere cannot acquire exclusive write access to the disk, which is required before the VM can be powered on.
CentOS 7.0 64-bit is a fully supported guest operating system in vSphere and does not cause a power-on failure; the guest OS type only affects available VMware Tools and hardware compatibility settings.
Hyper-Threading is a BIOS and vSphere CPU scheduling feature that controls how logical processors are presented to VMs; enabling or disabling it does not prevent any VM from powering on.
Concept tested: VM power-on failure causes - VMDK locks and swap file access
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.troubleshooting.doc/GUID-F89D3EE7-D761-4D96-A152-0CE99A77BFD4.html
Topics
Community Discussion
No community discussion yet for this question.