Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What to do if the recording cannot be started after the VMware virtual machine is abnormally shut down

2025-02-04 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Network Security >

Share

Shulou(Shulou.com)05/31 Report--

This article will explain in detail what to do about the record that cannot be started after the VMware virtual machine is shut down abnormally. The content of the article is of high quality, so the editor shares it for you as a reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

The colleague of the company forced the shutdown, resulting in the virtual machine in the VMware could not be started, an error was reported: the virtual machine is in use, please obtain ownership, and still say that it cannot be used after obtaining it.

This blog post documents a solution that cannot be started after an abnormal shutdown of a VMWare virtual machine. The website of our center is deployed on a Windows XP virtual machine, but due to power problems, the physical machine where the virtual machine is located is always rebooted, sometimes forcing the virtual machine to shut down before the virtual machine is shut down properly. After the machine is rebooted, the virtual machine system always fails to start properly, and an error similar to the following pops up:

Cannot open the disk'C:\ VM-machines\ Windows XP-001\ Windows XP Professional-000001.vmdk' or one of the snapshot disks it depends on. Reason: Failed to lock the file.

This is because the virtual disk (.vmdk) itself has a disk protection mechanism, in order to prevent data loss and performance degradation caused by multiple virtual machines accessing the same virtual disk (.vmdk) at the same time, each time the virtual machine starts, the virtual disk (.lck (disk lock) file is used to lock the virtual disk (.vmdk). The .lck (disk lock) file is automatically deleted when the virtual machine is shut down. However, it may be because you shut down the virtual machine abnormally, and the virtual machine hasn't had time to delete the .lck (disk lock) file on your system, so the above error occurs the next time you start the virtual machine.

Solution 1:

1. Delete or migrate to other directories under all .lck files and folders under the VMware path of the virtual machine, and you can generally solve it.

2. If you start Windows of VMware again

Vista system failed. Try to right-click the error system of the virtual machine-> Settings- > Hardware- > Hard

Disk- > Utilities- > Map- > Mapping virtual hard disk to Z:\

3. Disconnect the virtual hard disk, reload and start. The system can be booted normally.

This is the solution I used to start the virtual machine normally.

Solution 2:

Use notepad to open the * .VMX file with a line of code disk.locking =

"FALSE" to restart the virtual machine. I haven't tested this method, so I'll make a record here for later use.

On the VMware virtual machine can not start after the abnormal shutdown record of what to do to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Network Security

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report