虚机打不开报failed to lock the file错误原因及解决方案
2017-01-10 11:20
417 查看
问题出现的原因:
虚拟磁盘(.vmdk)本身有一个磁盘保护机制,为了防止多台虚拟机同时访问同一个虚拟磁盘(.vmdk)带来的数据丢失和性能削减方面的隐患,每次启动虚拟机的时候虚拟机会使用扩展名为.lck(磁盘锁)文件对虚拟磁盘(.vmdk)进行锁定保护。当虚拟机关闭时.lck(磁盘锁)文件自动删除。但是可能由于您非正常关闭虚拟机,这时虚拟机还没来得及删除您系统上的.lck(磁盘锁)文件,所以当下次您启动虚拟机的时候出现了上述错误。
解决办法一:
1、在VMware该虚拟机路径下的所有.lck文件和文件夹下删除或迁移至其它目录,一般就可以解决了。
2、如果再次启动VMware的WindowsVista系统失败,尝试右键虚拟机出错的系统->Settings->Hardware->Hard Disk->Utilities->Map->映射虚拟硬盘到Z:/
3、断开虚拟硬盘,重新加载,启动。系统就可以正常启动了
经实验此办法以失败结束。如果有遇到Cannot open the disk '*.vmdk' or one of the snapshot disks itdepends on.Reason: Failed to lock the file错误的朋友不妨也试一下。如果您实验成功了,请给我们留言,以便我们进行更好的技术交流
解决办法二:
使用记事本打开*.VMX文件上加上一行代码disk.locking= "FALSE",重新启动该虚拟机。
使用方法二,问题得到解决,重新启动VMware正常启动,不会再出现Cannot open the disk '*.vmdk' or one of the snapshot disks itdepends on.Reason: Failed to lock the file.错误。
VMware “Cannot open the disk ‘XXXXXX.vmdk’or one of the snapshot disks it depends on.”
From time to time, I want to copy just theminimum files for a VMware virtual machine: the two .vmdk files and the .vmxfile. After moving those files to a new location or deleting a snapshot file,attempting to boot the virtual machine returns the following
error message:
Cannot open the disk ‘XXXXXX.vmdk’ or oneof the snapshot disks it depends on.
Reason: The system cannot find the filespecified.
I’ve found that following the steps belowfixes the problem and allows me to boot the virtual machine as it existed atthe time of creation. DO NOT USE these steps if you need to retain any changesto the machine:
Open the *.vmx file in a text editor andfind the line that refers to the old snapshot file, which will look somethinglike:
scsi0:0.fileName = “XXXXXX-000002.vmdk”
or
ide0:0.fileName = “XXXXXX-000002.vmdk”
Change the value to the filename of the~1kb .vmdk file (which happens to be the same as the name of the VM). Forexample, if your virtual machine was named “Windows XP Professional”, the linewould read:
scsi0:0.fileName = “Windows XPProfessional.vmdk”
Power on the VM. It should boot normally,but because the snapshot file is missing, the machine will boot to an earlierstate.
虚拟磁盘(.vmdk)本身有一个磁盘保护机制,为了防止多台虚拟机同时访问同一个虚拟磁盘(.vmdk)带来的数据丢失和性能削减方面的隐患,每次启动虚拟机的时候虚拟机会使用扩展名为.lck(磁盘锁)文件对虚拟磁盘(.vmdk)进行锁定保护。当虚拟机关闭时.lck(磁盘锁)文件自动删除。但是可能由于您非正常关闭虚拟机,这时虚拟机还没来得及删除您系统上的.lck(磁盘锁)文件,所以当下次您启动虚拟机的时候出现了上述错误。
解决办法一:
1、在VMware该虚拟机路径下的所有.lck文件和文件夹下删除或迁移至其它目录,一般就可以解决了。
2、如果再次启动VMware的WindowsVista系统失败,尝试右键虚拟机出错的系统->Settings->Hardware->Hard Disk->Utilities->Map->映射虚拟硬盘到Z:/
3、断开虚拟硬盘,重新加载,启动。系统就可以正常启动了
经实验此办法以失败结束。如果有遇到Cannot open the disk '*.vmdk' or one of the snapshot disks itdepends on.Reason: Failed to lock the file错误的朋友不妨也试一下。如果您实验成功了,请给我们留言,以便我们进行更好的技术交流
解决办法二:
使用记事本打开*.VMX文件上加上一行代码disk.locking= "FALSE",重新启动该虚拟机。
使用方法二,问题得到解决,重新启动VMware正常启动,不会再出现Cannot open the disk '*.vmdk' or one of the snapshot disks itdepends on.Reason: Failed to lock the file.错误。
VMware “Cannot open the disk ‘XXXXXX.vmdk’or one of the snapshot disks it depends on.”
From time to time, I want to copy just theminimum files for a VMware virtual machine: the two .vmdk files and the .vmxfile. After moving those files to a new location or deleting a snapshot file,attempting to boot the virtual machine returns the following
error message:
Cannot open the disk ‘XXXXXX.vmdk’ or oneof the snapshot disks it depends on.
Reason: The system cannot find the filespecified.
I’ve found that following the steps belowfixes the problem and allows me to boot the virtual machine as it existed atthe time of creation. DO NOT USE these steps if you need to retain any changesto the machine:
Open the *.vmx file in a text editor andfind the line that refers to the old snapshot file, which will look somethinglike:
scsi0:0.fileName = “XXXXXX-000002.vmdk”
or
ide0:0.fileName = “XXXXXX-000002.vmdk”
Change the value to the filename of the~1kb .vmdk file (which happens to be the same as the name of the VM). Forexample, if your virtual machine was named “Windows XP Professional”, the linewould read:
scsi0:0.fileName = “Windows XPProfessional.vmdk”
Power on the VM. It should boot normally,but because the snapshot file is missing, the machine will boot to an earlierstate.
相关文章推荐
- 打开VMware出现Reason: Failed to lock the file.错误的解决办法
- VMware vmdk错误: Failed to lock the file
- VMware "Failed to lock the file" 错误
- Project has no default.properties file! Edit the project properties to set one.错误解决方案
- Project has no default.properties file! Edit the project properties to set one.错误解决方案
- VM 启动报错 "Failed to lock the file"
- Project has no default.properties file! Edit the project properties to set one.错误解决方案
- IBM AppScan 7.8.1 更新安全规则库后出现“AppScan Severe Error: Failed to load rules/advisories file”错误的解决方案
- vmware, failed to lock the file
- VMware虚拟机出现Reason: Failed to lock the file
- failed due to the following error: 80070005 错误解决方案
- VMWare出现文件未能锁定(Failed to lock the file)的解决方法
- VMware虚拟机出现Reason: Failed to lock the file
- VMware启动系统报错,reason: failed to lock the file.
- fail to lock the file [ubuntu 系统崩溃的解决方案]
- VMWare出现文件未能锁定(Failed to lock the file)的解决方法
- vmware, failed to lock the file
- 强制关机 VMware Wrokstation Error (failed to get exclusive lock on the configuration file----)
- Project has no default.properties file! Edit the project properties to set one.错误解决方案
- VMware虚拟机出现Reason: Failed to lock the file