Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Investigating hosted virtual machine lock files (1003857)

Last Updated: 9/23/2018Categories: TroubleshootingTotal Views: 94845Language:
Chinese (Simplified)JapaneseSpanishEnglish

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Symptoms

Your virtual machine does not start.

You cannot boot your virtual machine.

You see one of these errors:

Cannot open the disk or one of the snapshot disks it depends on.

Failed to lock the file.

The virtual machine is already powered on.

Error while opening the virtual machine: no permission to access this virtual machine

Check for missing files failed.

Your host's BIOS does not have valid NUMA information.

Please update the host's BIOS or associate the virtual machine with the processors in a single NUMA node (CEC).

files-locked locked-vm-files lock-files non-deleted-lock-files vm-locked

Purpose

This article guides you through the process of determining if any lock files are preventing a virtual machine from being powered on.

Resolution

There are some circumstances in which one or more lock files exist in a virtual machine's directory even though the virtual machine is powered off. When this occurs, the only way that the virtual machine can be powered on is to manually remove the lock files.

The following steps provide information on how to remove lock files that are preventing a powered off virtual machine from powering on:

Verify that the virtual machine is powered off. For more information, see Investigating if a hosted virtual machine is powered on (1003844).

Warning: It is very important that you do not delete any lock files associated with a virtual machine if it is actually powered on. Doing so interferes with the virtual machine and may result in unrecoverable data loss.

Navigate to the location of the virtual machine's files. For more information, see Locating a hosted virtual machine's files (1003880).

Note: If different, the locations of the virtual machine configuration (.vmx) file as well as of all of the virtual disk files need to be checked in the following step.

Look for and delete any file, directory, or folder that ends in either .lck or .LOCKFILE . Please take a backup of the file before deleting until the issue is confirmed fixed.

If you are at a Windows command prompt and in the directory where the lock file exists, type del <filename> , where <filename> is the name of the file, and press Enter.

Note: If it is a directory, then type rd <directory> /s , where <directory> is the name of the directory, and press Enter.

If you are at a Linux shell prompt and in the directory where the lock file exists, type rm <filename> , where <filename> is the name of the file, and press Enter.

Note: If it is a directory, then type rm -rf <directory> , where <directory> is the name of the directory, and press Enter.

Related Information

Lock files are created when a virtual machine is powered on. Their purpose is to prevent multiple VMware processes from accessing the same virtual machine at the same time. The existence of a lock file indicates to VMware that the associated virtual machine is powered on. If a lock file exists, and an attempt is made to power on the virtual machine, VMware will prevent this and an error message will be displayed. The exact error message will vary, depending on the nature of the lock file, the product in use, and the version of the product.

Lock files are most often located in a virtual machine's directory in error when the virtual machine was shut down unexpectedly and the VMware product in use did not have time to perform the normal routine removal of these files.

Verificando arquivos de bloqueio da máquina virtual hospedada
检查托管的虚拟机锁定文件
ホスト型仮想マシンのロック ファイルを調査する

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
Verificação da integridade de arquivo da máquina virtual hospedada (1003846)

KB
•
ホストされた仮想マシンに対して十分なディスクの空き領域があることの確認 (1003856)

KB
•
验证虚拟机 TCP/IP 设置 (1007875)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workstation Player

VMware Workstation

VMware Server

VMware Player

VMware GSX Server

VMware ACE

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant