What are three reasons why a virtual machine might fail to power on? (Choose three.)
A. The virtual machine is running on an ESXi host which has an expired license.
B. The virtual machine is running on a datastore which has insufficient disk space for the .vswp file.
C. The virtual machine is in a cluster with vSphere HA Admission control enabled.
D. The virtual machine has a disconnected network adapter.
E. The virtual machine does not have a Virtual Hard Disk assigned.
Correct Answer: ABC
Explanation/Reference:
Explanation:
When a virtual machine fails to power on, a reason may be logged to the vmware.log file for the virtual machine, to the management agent logs, or presented in the client. Review any messages and consider these points:
1.The virtual machine monitor may be asking a QUESTIONto be answered during startup. A virtual machine may pause the power-on task at 95% toobtain additional information from the administrator. For more information, see Powering on a virtual machine pauses at 95% while waiting for a QUESTIONto be answered (1027096).
2.Creating a new power-on task may fail if another task for the virtual machine or other component is already in progress, and multiple concurrenttasks on the object are not permitted. For more information, see:
Collecting information about tasks in VMware ESX and ESXi (1013003) vCenter operation times out with the error: Operation failed since another task is in progress (1004790).
3.A virtual machine may fail to power on if licensing requirements are not met. For more information, see:
Cannot Power on Virtual Machines, "Not enough licenses installed to perform the operation" Error Message (7114568)
The Managing ESX/ESXi and vCenter Server Licenses section of the Datacenter Administration Guide for vSphere 4 or higher
The VirtualCenter and ESX Server Licensing Overview section of the Installation Guide for VMware Infrastructure 3
4.The virtual machine may be configured to reserve physical memory on the host, but the host memory is over-committed and the required memory isunavailable.
For more information, see:
Virtual machine does not power on when there is high CPU reservation (1001637)
Powering on a virtual machine fails with the error: memoryAllocation.reservation (1036914).
5.The virtual machine may be starting in a VMware High Availability cluster with strict admission control enabled, and there are insufficient resourcesto guarantee failover for all virtual machines. For more information, see:
Implications of enabling or disabling VMware HA strict admission control when using DRS and VMware DPM (1007006)
Diagnosing insufficient fail over capacity on a VMware High Availability Cluster (1003717)
Automating High Availability (HA) Services with VMware HA whitepaper
6.A file required for starting the virtual machine, such as a virtual disk or swap file, may be unavailable or missing. For more information,see Investigating virtual machine file locks in ESX/ESXi (10051).
7.The virtual machine may have been previously suspended and making use of CPU features which are unavailable or incompatible with the CPUfeatures available on this host. The virtual machine cannot be started without the required features. For more information, see:
Powering on a virtual machine from a suspend state or reverting to a snapshot fails (1038218)
Virtual machines fail to power on due to a suspend state from an incompatible CPU type (1000241)
To retain the suspended state, move the virtual machine back to the host it was originally suspended on and power-on the virtual machine there. To discard the suspend state, and power on the virtual machine in a crash-consistent manner, see Unable to power on a suspended virtual machine using vSphere Client (1004606).
8.The virtual machine may require both a VT-capable CPU and the VT feature to be enabled in the host system’s BIOS. This is true for all 64-bitvirtual machines. If the VT feature is unavailable, the virtual machine may produce the message msg.cpuid.noLongmode. For more information, see Enabling VT on Intel EM64T Systems for ESX Server 3 (3282933).
9.The virtual machine may require another CPU feature which is unavailable on this host. The virtual machine may produce a message similarto msg.cpuid.<FeatureName>, identifying the specific feature it has been configured to require. Move the virtual machine back to the host which has the required CPU features, or edit the virtual machine’s configuration to remove the requirement.
10.The virtual machine may start, but quickly fail with an error during startup. Review the contents of the vmware.log file in the virtual machine’sdirectory for any errors or warnings, and search the Knowledge Base for the error or warning. Base your troubleshooting on the specific messages seen in the logs. For more information, see:
Determining why a virtual machine was powered off or restarted (1019064) Interpreting virtual machine monitor and executable failures (1019471)
11.If the virtual machine does successfully power on, but the guest OS doesn’t start correctly, there may be an incompatibility between the virtualhardware and drivers within the guest OS. For example, a missing SCSI driver may be required for booting. For more information, see Windows virtual machine configured to use a BusLogic SCSI controller reports that the operating system does not support the controller (2007603).
12.If the guest OS, or a driver or application within the virtual machine experiences a problem during startup, the guest OS may becomeunresponsive. Continue troubleshooting. For more information, see Troubleshooting unresponsive guest operating system issues (1007818).
Reference:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2001005
Explanation/Reference:
Explanation:
When a virtual machine fails to power on, a reason may be logged to the vmware.log file for the virtual machine, to the management agent logs, or presented in the client. Review any messages and consider these points:
1.The virtual machine monitor may be asking a QUESTIONto be answered during startup. A virtual machine may pause the power-on task at 95% toobtain additional information from the administrator. For more information, see Powering on a virtual machine pauses at 95% while waiting for a QUESTIONto be answered (1027096).
2.Creating a new power-on task may fail if another task for the virtual machine or other component is already in progress, and multiple concurrenttasks on the object are not permitted. For more information, see:
Collecting information about tasks in VMware ESX and ESXi (1013003) vCenter operation times out with the error: Operation failed since another task is in progress (1004790).
3.A virtual machine may fail to power on if licensing requirements are not met. For more information, see:
Cannot Power on Virtual Machines, "Not enough licenses installed to perform the operation" Error Message (7114568)
The Managing ESX/ESXi and vCenter Server Licenses section of the Datacenter Administration Guide for vSphere 4 or higher
The VirtualCenter and ESX Server Licensing Overview section of the Installation Guide for VMware Infrastructure 3
4.The virtual machine may be configured to reserve physical memory on the host, but the host memory is over-committed and the required memory isunavailable.
For more information, see:
Virtual machine does not power on when there is high CPU reservation (1001637)
Powering on a virtual machine fails with the error: memoryAllocation.reservation (1036914).
5.The virtual machine may be starting in a VMware High Availability cluster with strict admission control enabled, and there are insufficient resourcesto guarantee failover for all virtual machines. For more information, see:
Implications of enabling or disabling VMware HA strict admission control when using DRS and VMware DPM (1007006)
Diagnosing insufficient fail over capacity on a VMware High Availability Cluster (1003717)
Automating High Availability (HA) Services with VMware HA whitepaper
6.A file required for starting the virtual machine, such as a virtual disk or swap file, may be unavailable or missing. For more information,see Investigating virtual machine file locks in ESX/ESXi (10051).
7.The virtual machine may have been previously suspended and making use of CPU features which are unavailable or incompatible with the CPUfeatures available on this host. The virtual machine cannot be started without the required features. For more information, see:
Powering on a virtual machine from a suspend state or reverting to a snapshot fails (1038218)
Virtual machines fail to power on due to a suspend state from an incompatible CPU type (1000241)
To retain the suspended state, move the virtual machine back to the host it was originally suspended on and power-on the virtual machine there. To discard the suspend state, and power on the virtual machine in a crash-consistent manner, see Unable to power on a suspended virtual machine using vSphere Client (1004606).
8.The virtual machine may require both a VT-capable CPU and the VT feature to be enabled in the host system’s BIOS. This is true for all 64-bitvirtual machines. If the VT feature is unavailable, the virtual machine may produce the message msg.cpuid.noLongmode. For more information, see Enabling VT on Intel EM64T Systems for ESX Server 3 (3282933).
9.The virtual machine may require another CPU feature which is unavailable on this host. The virtual machine may produce a message similarto msg.cpuid.<FeatureName>, identifying the specific feature it has been configured to require. Move the virtual machine back to the host which has the required CPU features, or edit the virtual machine’s configuration to remove the requirement.
10.The virtual machine may start, but quickly fail with an error during startup. Review the contents of the vmware.log file in the virtual machine’sdirectory for any errors or warnings, and search the Knowledge Base for the error or warning. Base your troubleshooting on the specific messages seen in the logs. For more information, see:
Determining why a virtual machine was powered off or restarted (1019064) Interpreting virtual machine monitor and executable failures (1019471)
11.If the virtual machine does successfully power on, but the guest OS doesn’t start correctly, there may be an incompatibility between the virtualhardware and drivers within the guest OS. For example, a missing SCSI driver may be required for booting. For more information, see Windows virtual machine configured to use a BusLogic SCSI controller reports that the operating system does not support the controller (2007603).
12.If the guest OS, or a driver or application within the virtual machine experiences a problem during startup, the guest OS may becomeunresponsive. Continue troubleshooting. For more information, see Troubleshooting unresponsive guest operating system issues (1007818).
Reference:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2001005
