The Virtual Machine on esxi5.1 was deleted without careful check.

The VM was deleted. Fortunately, there was a hard disk file XX. vmdk while taking the snapshot. I found some online solutions to solve the problem. To sum up:

1. Create a vm a in custom mode, but do not create a hard disk. Virtual Machine A can be different from the original one, but it is best to be consistent (both can be completed in my test)

2. log on to the esxi host using SSH. Remember to enable and allow SSH logon.

3. Go to the directory left by the original snapshot, find the vmdk file, and run the LS-Al command to view the current XX. vmdk size. Enter the directory of vm a and run the vmkfstoos command to create a new file named A. vmdk, which is the same size as the XX. vmdk file.

The command format is as follows: vmkfstools-C file size-A lsilogic A. vmdk

4. Use the previously reserved XX. vmdk file to replace the added a. vmdk file. Use SSH to log on to the esxi host and overwrite it with the CP command. Remember to use a. vmdk as the file name.

5. Start the VM.

This article from the "standing on the shoulders of giants to see the world" blog, please be sure to keep this source http://lixiaotao.blog.51cto.com/985722/1551239

The Virtual Machine on esxi5.1 was deleted without careful check.