A virtual machine with a snapshot may have an error when making an online storage vmotion, which will cause the VM to turn on the virtual machine again, with the following errors.
650) this.width=650; "src=" Https://s3.51cto.com/wyfs02/M02/8D/B7/wKiom1im_NODALsEAAKPlkVjqZ8448.jpg "title=" 1653371960.jpg "alt=" Wkiom1im_nodalseaakplkvjqz8448.jpg "/>
There are three ways to solve these problems:
1. See if there is a. lck file or folder in the virtual machine directory, and delete all if any.
2. To see if the CID value of the vmdk file and the snapshot's vmdk file matches, refer to document: HTTPS://KB.VMWARE.COM/SELFSERVICE/SEARCH.DO?CMD=DISPLAYKC&DOCTYPE=KC &doctypeid=dt_kb_1_1&externalid=1007969
is an example of a CID mismatch:
650) this.width=650; "src=" Https://s1.51cto.com/wyfs02/M00/8D/B7/wKiom1inA_aiwzy5AAEy_wC_Hp0449.png "title=" Qq20170217220441.png "alt=" Wkiom1ina_aiwzy5aaey_wc_hp0449.png "/>
3, if your fault situation does not belong to the above two, neither Lck file, cid value is also matched, then the last method left: Restart Dafa, restart the physical machine, the problem should be resolved.
This article is from "I'm Still alive" blog, please be sure to keep this source http://hujizhou.blog.51cto.com/514907/1898964
"Failed to lock file" error occurred on VMware vsphere virtual machine