Loading...
Loading...
When attempting to start up a virtual machine (VM), it fails to power on.
This resource provides a guide to identify symptoms and align them with solutions to resolve the failure of virtual machines to power on/VM power-on issues.
The failure of a VM to power on may be caused by any of the following reasons: ESXi OS problemsFile corruptionFile locksGuest OS problemsLicense problemsNetwork problemsStorage Array/Datastore problemsUser permissionsVM configuration problemsVM snapshot problemsVM unfinished tasksvCenter OS problems
VM power-on failures may impact the ability of significant numbers of users to work.However, some resolutions can lead to data loss. As a result, please exercise caution when this risk is highlighted below.
General symptoms: SymptomsCausesResolutionsGuest OS doesn't load properly Guest OS file/partition corruptionVM configurationVirtual hardware/guest OS driver incompatibility Troubleshooting unresponsive guest operating system issuesMicrosoft Cluster VM won't power on after disk provisioning changeWrong disk provisioning, such as, not using Thick, eager-zeroed provisioning Check and convert disks to supported provisioning per About Setup for Windows Server Failover Clustering on VMware vSphere.For more information see Setup for Failover Clustering and Microsoft Cluster Service Power on task hangs ESXi OS problemvCenter OS problemvCenter/ESXi communication problem Virtual machine power on task hangsVM name shows as a path Communication problems between ESXi hosts and arrayDatastore problems/corruptionStorage array configurationStorage array problems Virtual machines names appear as ds:///vmfs/volumes/datastore/vm_nameVM power on option greyed out in vCenter ESXi OS problemvCenter OS problemvCenter/ESXi communication problem Virtual Machine Power On/Off options greyed out on vCenter Server clientVM orphaned or invalid in vCenter UI Usually problems accessing datastore containing VM filesVirtual machines appear as invalid or orphaned in vCenter Server vCenter/ESXi host UI messages: SymptomsCausesResolutionsA file was not found• Datastore errors Datastore missingVM descriptor file not updating for disk changesVirtual disk descriptor file problemVirtual disk file missing Unable to power on virtual machine with Error: Can't open 'vmfs/volumes/.vmdk': Could not find the file"A general system error occured: vDS host errorvCenter Server database problem with VM virtual nic recordsUnable to power on virtual machine with Error: A general system error occurred: vDS host errorA specified parameter was not correct. memoryAllocation.reservationVM memory reservation that is greater than the memory limit set on that same virtual machinePowering on a virtual machine fails with the error: memoryAllocation.reservationAnother task is already in progressAnother VM task, such as disk consolidation is in progress, or is hungVirtual machine power on task hangsAPIC ID mismatchVM virtual hardware doesn't support the guest OS requirementsUnable to power on virtual machine with Error: APIC ID mismatchBad addressStorage communication problemsStarting a virtual machine from the command line on VMDK file/files fails with the error: Bad addressCan't open '/vmfs/volumes/<vm file path>.vmdk' : Could not find the file Datastore errorsDatastore missingVM descriptor file not updating for disk changesVirtual disk descriptor file problemVirtual disk file missing Unable to power on virtual machine with Error: Can't open 'vmfs/volumes/.vmdk': Could not find the file"Cannot open the disk '/vmfs/volumes/<vm file path>.vmdk' or one of the snapshot disks it depends on. Change tracking file problemDatastore problemFile lock problemMemory allocation problemParent virtual disk modifiedVirtual disk problem Powering on a virtual machine fails with the error: Cannot open the diskCannot use host <hostname> because the host's CPU is not compatible with the virtual machine's suspend stateVM state was suspended or snapshot with memory included, then moved to a new host with different CPU featuresPowering on a virtual machine from a suspend state or reverting to a snapshot failsCould not open change tracking filesChange tracking file is not clearing“could not open/create change tracking files” error when powering on VMcpu min outside valid rangeCPU minimum reservation value outside the range the physical CPU can serveVirtual machine does not power on when there is high CPU reservationDevice 'Bootstrap' is not available Most commonly, attempting to power on a VM on a host that does not hold the lock on the VM files.ESXi has insufficient access to underlying storageBad data in the VM descriptor file (*.vmx) Error Device 'Bootstrap' is not available when powering on a VM on ESXi 6.0Device 'HotPlugManager' is not availableMaking configuration changes on powered-on VM which shares virtual disks with other VMs Check if VM shares a disk with other VMsPower off VM before making configuration changes Error 32 (Broken pipe)Two processes try to talk to each other over a connection (called a pipe) and one of the processes unexpectedly disappears Power off or suspend the virtual machine if it is runningPower the VM on again Incompatible device backing specific for device ‘0’Virtual disk provisioning changed after Storage vMotionFailed to power on a machine with the error ‘Incompatible device backing specific for device ‘0’, after storage vMotion to vSAN datastoreInvalid CPU allocation requested for VMCPU minimum reservation value outside the range the physical CPU can serveVirtual machine does not power on when there is high CPU reservationFailed to enumerate disks Virtual disk files are not accessible due to: File locks held by other ESXi hostsAccess permission being blocked by storage arrayStorage array problemsBad information in virtual machine descriptor fileBad information in virtual disk descriptor fileBad virtual disk data file (*-flat.vmdk) Check that permissions for the ESXi host to access the storage is not being blocked at the storage array. Check access control lists, and so forth. Also see: Powering on a virtual machine fails with the error: File system specific implementation of Ioctl[file] failed Failed to initialize swap file Most commonly, datastore out of spaceFile lock problemsDatastore problems Unable to power on virtual machine with Error: Failed to initialize swap fileFailed to lock the file File lock problemsInvestigating virtual machine file locks on ESXi hostsFailed to find a host for powering on the virtual machine VM resource reservations higher than host can serveCPU incompatibility between VM and ESXi host Virtual Machine not Compatible with any Host Failed to revert the execution state of the virtual machine <vm name> on host <host name>VM state was suspended or snapshot with memory included, then moved to a new host with different CPU featuresPowering on a virtual machine from a suspend state or reverting to a snapshot failsFeature 'bad_requirement:hv.capable' was 0, but must be at least 1.Affects vCLS cluster management appliances when using nested virtual ESXi hosts in 7.xSupport for running ESXi/ESX as a nested virtualization solutionFeature requirements of this virtual machine exceed capabilities of this host's current EVC modeVM state was suspended or snapshot with memory included, then moved to a new host with different CPU featuresPowering on a virtual machine from a suspend state or reverting to a snapshot failsFile system specific implementation of GetPageRef[file] failedUnable to read virtual machine filePowering on a virtual machine fails with the error: File system specific implementation of Ioctl[file] failedFile system specific implementation of Ioctl[file] failed Bad entries in virtual disk descriptor files (*.vmdk, *.vmx)Communication problems between ESXi host and storage arrayESXi OS problemsProblems with file locksVirtual disk data corruption Powering on a virtual machine fails with the error: File system specific implementation of Ioctl[file] failedFile system specific implementation of LookupAndOpen[file] failedVirtual disk files not opening properlyVM fails to power on with Error: "File system specific implementation of LookupAndOpen [file] failed"Insufficient capacity on each physical CPUCPU reservation higher than ESXi host can supportPowering on a virtual machine fails with the error: Insufficient capacity on each physical CPUInvalid CPU allocation requested for VMCPU reservation higher than ESXi host can supportPowering on a virtual machine fails with the error: Insufficient capacity on each physical CPULicense not available or other license-related errorUsually exceeded license or wrong type of license applied to ESXi hosts or vCenter Server See Licensing ESXi 6.x/7.0.x and vCenter Server 6.x/7.0.x See vSphere Virtual Machine AdministrationContact your license vendor Module 'CheckpointLate' power on failedVM state was suspended or snapshot with memory included, then moved to a new host with different CPU featuresPowering on a virtual machine from a suspend state or reverting to a snapshot failsModule 'Disk' power on failed. Change tracking file problemDatastore problemFile lock problemMemory allocation problemParent virtual disk modifiedVirtual disk problem Powering on a virtual machine fails with the error: Cannot open the diskModule MonitorLoop Power on FailedThe MonitorLoop program module detected that the VM did not power on. This is a high level message.Look at the message details reported in the user interface. Follow the box in this article that aligns with the details.msg.cpuid.FeatureName VM requires a CPU processor feature which ESXi host is not providingUnable to power on virtual machine with Error: "msg.cpuid."No host is compatible with the virtual machine Virtual Machine not Compatible with any Host VM Power On failed. No host is compatible with the VMOne of the parameters supplied is invalidThe Virtual SAN cluster UUID has changedVirtual SAN cluster UUID changes may result in VM power-on failuresPBM error occurred during PreReconfigureCallbackManually copying VM files from traditional storage to vSANFlat VMDK on vSANThe attempted operation cannot be performed in the current state (Powered on) from the HostControl of VM processes lost to ESXi host Ensure no critical process such as snapshot consolidation is running on the VM per Virtual machine power on task hangsIf no critical process is running, follow Unable to Power off a Virtual Machine in an ESXi host to shut down the processes The available Memory resources in the parent resource pool are insufficient for the operation VM memory reservation settings higher than host can supportESXi OS problemvCenter Server OS problemvCenter/ESXi host communication problemESXi host server hardware configuration problem Unable to power on VM with Error: The available Memory resources in the parent resource pool are insufficient for the operationThe features supported by the processors in this machine are different from the features supported by the processors in the machine on which the checkpoint was saved.VM state was suspended or snapshot with memory included, then moved to a new host with different CPU featuresPowering on a virtual machine from a suspend state or reverting to a snapshot failsThe file specified is not a virtual disk (15)The .vmdk descriptor file for the virtual machine boot disk is corrupt or missingPowering on the virtual machine fails with the error: The file specified is not a virtual disk (15)The operation is not allowed in the current state A critical process is runningA VM has hung processes Virtual machine power on task hangsThe parent virtual disk has been modified since the child was createdParent to a snapshot virtual disk file has been changed after the snapshot was taken "The parent virtual disk has been modified since the child was created" error A virtual machine cannot boot after resizing a base virtual machine disk (VMDK) that is part of a snapshot chain The specified device is not a valid physical disk deviceUsually VM files put into ESXi host's scratch partitionVirtual machine operations on a ESXi 6.0 host fails with the error: The specified device is not a valid physical disk deviceThe virtual CPU performance counter events are not compatible with the host CPU.VM state was suspended or snapshot with memory included, then moved to a new host with different CPU featuresPowering on a virtual machine from a suspend state or reverting to a snapshot failsThe VM failed to resume on the destination during early power on The destination file system does not support large files.Failed to lock the file.Could not open/create change tracking file.Cannot allocate memoryNo such deviceThe file specified is not a virtual diskInsufficient permission to access file Migrating a virtual machine fails with the error: The VM failed to resume on the destination during early power on : ReasonThere is no more space for virtual disk VM.vmdkUsually datastore VM files are on is out of space, very commonly seen when snapshots are created by backup software and fill remaining space quickly There is no more space for virtual disk '.vmdk'"There is no more space for virtual disk .vmdk" error when starting vSAN VM Transport (VMDB) error -45: Failed to connect to peer processUsually temporary network errors due to congestion Retry power on after a few minutes About vSphere Monitoring and PerformanceCheck for messages about network errorsCheck for performance issues per Unable to access file /vmfs/volumes/<filepath>.vmdk since it is lockedMost commonly, powered on VM contains locks on all files in use by the owning ESXi host to facilitate read and write access.Troubleshooting issues resulting from locked virtual disksUnable to access -000001.vmdk.ctkChange tracking file is not clearing“could not open/create change tracking files” error when powering on VMUnable to write VMX file Lock on VM descriptor file (*.vmx) held by another ESXi host*.vmx file corruption Rule out file lock problems per Investigating virtual machine file locks on ESXi hostsIf file locks are not the issue, follow Recreate a lost or deleted virtual machine .vmx configuration file on an ESXi host Unsupported and/or invalid disk typeVM for VMware Hosted product (VMware Workstation, VMware Player, VMware Fusion) powered on an ESXi hostA virtual machine fails to power on with the error: Unsupported and/or invalid disk typeVirtual disk 'Hard disk 2' is a mapped direct-access LUN that is not accessibleThe host attempting to start or receive the virtual machine cannot access the device (LUN) backing the raw disk mappingPowering on or migrating a virtual machine fails with the error: Virtual Disk 'X' is a mapped direct access LUN that is not accessibleVirtual machine disk consolidation is needed Snapshots requiring more resources than ESXi host can handleSnapshot chain problemsSnapshots exceed other limitations Troubleshooting virtual machine snapshot descriptor problemsvmdk file is missing Datastore errorsDatastore missingVM descriptor file not updating for disk changesVirtual disk descriptor file problemVirtual disk file missing Unable to power on virtual machine with Error: Can't open 'vmfs/volumes/.vmdk': Could not find the file"
Please refer to these relevant resources for additional information: Troubleshooting virtual machine power on task hangsFusion virtual machines fail to start after upgrading Mac OS XTroubleshooting Fusion startup issuesTroubleshooting Fusion virtual machine startup issues
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.