Today I discovered that there is an issue with VCB(mounter) and .vmx/.vmdk placement.
For some reason, our P2V tool had placed all config files (.vmx, log files, etc.) on /vmfs/volumes/datastore 1/<Servername> and our .vmdk files on /vmfs/volumes/datastore 2/<Servername>. In a normal environment, config files and vmdk files are kept together.
As you can see in the screenshot, the initial snapshot gets created but no operations can be performed and a timeout occurs after 45 minutes.
vcbMounter created a snapshot, and placed the snapshot files by default in the /vmfs/volumes/datastore 1/<Servername> folder where our .vmx resides. For some reason, VCB(mounter) is not able to “find” our original .vmdk files.
You have 2 options in this scenario:
- If you don’t want to have your .vmx and your .vmdk files togheter: change the Virtual Machine Working Location from the location where the .vmx file resides to the datastore location where the .vmdk files reside and (re)add to the VirtualCenter inventory.
This can be done by editing the .vmx file and adding the following parameter:
workingDir = "/vmfs/volumes/454b27d2-f2172987-4798-0017085ce0dd/<ServerName>/"
Note the UID notation, and not the linked name
- If you want your .vmx and .vmdk files together: migrate your VM using a “cold" migration and relocate your .vmx (configuration files) to the datastore where your .vmdk files reside (see also my previous article here). This is the easiest & fastest approach.