VMware VLM3-ENG-CP User Guide - Page 155
Importing a Virtual Machine as a Template Fails, Importing a Virtual Machine from VMFS Storage Fails
View all VMware VLM3-ENG-CP manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 155 highlights
Chapter 8 Troubleshooting Lab Manager Importing a Virtual Machine as a Template Fails Problem I try to import a virtual machine to serve as a template and see this error message: Disk too large to import. Consider using 'VMware vdiskmanager' to split the large disk. Solution You can import virtual machines up to 2GB per .vmdk file. For monolithic templates that exceed the size limit, create split disks using the VMware Virtual Disk Manager utility packaged with Workstation. For instructions on using this utility, see the "Using Disks" chapter of the VMware Workstation User's Manual. Importing a Virtual Machine from VMFS Storage Fails Problem I try to import a virtual machine from VMFS storage to serve as a template. This error message appears: The source VM's vmx configuration file and vmdk disk file(s) must all reside in the same directory on the VMFS volume. Solution To import a virtual machine with an absolute path to its .vmdk file into Lab Manager, review these requirements: The .vmdk files have to reside in the same directory as the .vmx file. The path to a .vmdk file must be relative to the virtual machine. For example, if a .vmx file is in [storage1] abc/abc.vmx, the .vmdk path in the .vmx file must be abc.vmdk. You cannot use /vmfs/volumes/storage1/abc/abc.vmdk. If you need to import a virtual machine with an absolute path to its .vmdk file, power off the virtual machine, open its .vmx file, and make the path relative to the .vmx file. VMware, Inc. 155