Validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.
-
Verify that the destination has sufficient space on the file system to accommodate the new virtual machine. Check the free space on the destination before attempting to convert. In addition, the source server must have at least 200 MB of free space per volume for conversion to be successful. For help identifying free space for your virtual machine, see
Verifying sufficient free disk space for an ESX/ESXi virtual machine (1003755).
-
Verify that the destination supports large files. If the conversion is to a standalone virtual machine and the destination is being accessed via UNC or SMB shares, consider these points:
-
The destination file system must support files larger than 2GB, like NTFS or ext3.
-
If quotas are implemented, ensure that there is enough free space remaining within the quota for the virtual machine. If you are unable to specify a UNC path as the destination, use a mapped drive letter instead.
Note: Certain Linux/Samba server configurations may prevent Converter from detecting the correct destination file size limit. If the problem persists, use a Windows-based server file share.
For more information, see Conversion fails when source or destination do not support large files (1008633).
-
-
Confirm that you have the correct permissions on the destination to write files. If the destination is an ESX/ESXi host or vCenter Server, ensure that the account used also has permissions to create a virtual machine on in the destination container. For more information, see
User with 'Create' privilege cannot create virtual machines (1004417).
-
Note: If your problem still exists after trying the steps in this article, please file a support request with VMware Support and note this KB Article ID (1006285) in the problem description. For more information, see
How to Submit a Support Request.