VMware

VMware Virtual Machine Importer 2 Release Notes

Features | Documentation | Knowledge Base | Discussion Forums

Notes on VMware Virtual Machine Importer 2, Build 30557

Build 30557 is a release build of VMware Virtual Machine Importer.

The release notes contain the following:

Help and Feedback

We have created a Virtual Machine Importer Discussion forum on the VMware Technology Network (VMTN) at www.vmware.com/community/forum.jspa?forumID=221&start=0. Please use this forum to report problems, request help, and provide feedback on this VMware Virtual Machine Importer release.

Installation Notes

This VMware Virtual Machine Importer 2 installation may interfere with the following VMware product versions, and cannot be installed alongside them:

  • VMware VirtualCenter 1.x Management Server
  • VMware VirtualCenter 2.0 Management Server
  • VMware P2V 1.x and 2.x
  • VMware Consolidated Backup 1.0

Note that VMware Virtual Machine Importer 2 can safely be installed alongside the VirtualCenter/VI Client

Uninstalling VMware Virtual Machine Importer 2 will cause import functionality in VMware Workstation 5.5.0/5.5.1 and VMware Server 1.0 to fail. This problem is resolved by upgrading to Workstation 5.5.2 or VMware Server 1.0.1.


Platforms

VMware Virtual Machine Importer 2 can be installed on the following platforms:

  • Windows 2000 Professional
  • Windows 2000 Server
  • Windows XP Professional
  • Windows 2003 Server

VMware Virtual Machine Importer 2 cannot be installed on Windows NT 4.

All target operating systems should have the latest patches available from Microsoft as of the release of this product. Installation of VMware Virtual Machine Importer 2 requires Windows Installer 3.1, which can be obtained here:
http://support.microsoft.com/?id=893803


Interoperability

VMware Virtual Machine Importer 2 supports the following sources and destinations:

 Import from Various Third-Party Formats
and VMware Products
 Export to a Virtual Machine for
VMware Workstation and Datacenter Products
  • Microsoft Virtual PC and Virtual Server
  • Symantec Backup Exec System Recovery images1
  • VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x)
  • VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.0)
  • VMware ESX Server 3.0
  • VMware VirtualCenter 2.0
  • VMware ESX Server 2.5.x (when managed by VirtualCenter 2.0)
  • VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x, ESX Server 2.5.x)
  • VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.0)2
  • VMware ESX Server 2.5.x (when managed by VirtualCenter 2.0)
  • VMware ESX Server 3.0 (when managed by VirtualCenter 2.0)
  • VMware ESX Server 3.0 (standalone)
Not Supported:
  • VMware ESX Server 2.5.x when managed by VirtualCenter 1.x
  • VMware ESX Server 2.5.x standalone

1. The Symantec family of products includes the Backup Exec System Recovery (formerly LiveState Recovery) products and the Norton Ghost 9 (and higher) products. Only images from the Backup Exec System Recovery products are fully supported, but images from Norton Ghost 9 (and higher) are likely to work.

2. Only Workstation 5.5 can power on linked imports of .sv2i images.


Supported Guest Operating Systems

The following 32-bit guest operating systems are fully supported by VMware Virtual Machine Importer 2:

  • Windows NT
  • Windows 2000 Professional
  • Windows 2000 Server
  • Windows XP Professional
  • Windows 2003 Server

Support for the following guest operating systems is Experimental. VMware Virtual Machine Importer 2 can clone source images containing these operating systems, but the destination virtual machine may or may not work without additional configuration after import. In particular, if the source image contains unsupported hardware, you may need to modify the configuration of the destination virtual machine before using it:

  • Linux
  • Windows NT 3.x
  • Windows ME
  • Windows 98
  • Windows 95
  • MS-DOS
  • 64-bit guest operating systems


Known Issues

This VMware Virtual Machine Importer 2 contains the following known issues:

GENERAL

Imported virtual machines with non-standard boot order may not boot
A virtual machine imported from a source virtual machine containing multiple disks where the boot disk is in an unusual position may not boot properly. Workaround: Adjust the BIOS configuration of the destination virtual machine to specify the correct boot disk.

"You are running out of disk space on Local Disk (X:)"
When Virtual Machine Importer is running on Windows XP and importing images that have very little free space, Windows XP may display warnings like "You are running out of disk space on Local Disk (X:) To free space on this drive by deleting old or unnecessary files, click here." This message can safely be ignored.

VMware Virtual Mount Manager Extended service is not uninstalled
The VMware Virtual Mount Manager Extended service service is used by other VMware products, including VM Importer 1.x, DiskMount 3 (GSX), and DiskMount 5.5 (Workstation). If no other VMware products are installed, Virtual Machine Importer should uninstall this service when it is uninstalled, but does not under some conditions. Workaround: If you have no other VMware products installed, the VMware Virtual Mount Manager Extended service can safely be disregarded. If you prefer, you can stop the service, unregister it (enter "cd \Program Files\Common Files\VMware\VMware Virtual Image Editing" followed by "vmount2 /unregserver" at a command prompt) and remove the directory \Program Files\Common Files\VMware\VMware Virtual Image Editing.

Under rare circumstances, Virtual Machine Importer might interpret Windows volumes as Posix
In certain situations (such as when there are no drive letters available), the importer might incorrectly determine the filesystem type of Windows volumes. In these situations, reconfiguration of the target virtual machine is not performed. Workaround: Ensure that there is at least one available drive letter before performing an import.

Running multiple simultaneous import operations on the same host can cause instability
Running multiple simultaneous import operations on the same host is not supported. Workaround: Do not run concurrent imports on a single host.

Importing a source virtual machine with a missing boot partition will not boot
Virtual Machine Importer should display a warning when this situation is detected, but does not.

Terminating Virtual Machine Importer during an import operation might cause import services to fail
If you select the importer task in the Task Manager and click on End Task, import services might fail. Workaround: Restart the VMware Virtual Machine Importer and VMware Virtual Mount Manager Extended services.

Log file is not displayed in some cases when import is cancelled
In some situations, after cancelling an import operation the log files are not available for display. Workaround: Retrieve the logs manually.

Uninstalling Virtual Machine Importer 2 causes import functionality in WS 5.5 and Server to fail
Uninstalling Virtual Machine Importer 2 causes import functionality in VMware Workstation 5.5 and VMware Server 1.0 to fail. Workaround: Re-install VMware Workstation 5.5.2 or VMware Server 1.0.1.


ESX SERVER AND VIRTUALCENTER

Poor copy performance has been observed importing to ESX Server 3 destinations when running in a virtual machine
On occasion, when Virtual Machine Importer is running in a virtual machine, imports to ESX Server 3 destinations have taken inordinately long times.

Unable to edit USB settings after import to ESX Server
After importing a virtual machine containing USB ports to ESX Server, you may be unable to edit the USB port settings of the destination virtual machine using the Virtual Infrastructure Client.

Destination ESX Server 2.5 virtual machine doesn't boot when source image contains Windows dynamic disks
Although the import of source images containing Windows dynamic disks to ESX Server 2.5 appears to succeed, the resulting virtual machine may fail to boot.

Importing the ESX Server requires 2x temporary space
When importing to ESX Server, Virtual Machine Importer requires available disk space to be twice the size of the image being imported.

Simultaneous imports of the same ESX source virtual machine are not supported
When importing the same virtual machine multiple times, only the first import will succeed.

Virtual Machine Importer fails to import ESX 2.5 virtual machine with a SCSI non-passthrough raw disk mount
When attempting to import an ESX 2.5 virtual machine that contains a SCSI non-passthrough raw disk mount (RDM) disk, the importer reports the error "Unable to import a virtual machine that uses disk partitions as virtual disks."

Problems booting imported virtual machine with mixed SCSI and IDE disks
Under certain circumstances when importing a source image that contains both SCSI and IDE disks, the destination virtual machine might fail to boot. Workaround: Edit the BIOS settings of the destination virtual machine to make sure that the correct boot disk is specified.


WORKSTATION, GSX SERVER, AND VMWARE SERVER

Virtual Machine Importer unnecessarily creates a .vmxf file and "scripts" directory when importing to Workstation 4
When importing to Workstation 4 destinations, Virtual Machine Importer creates an unused .vmxf file and "scripts" directory. This file and directory can safely be removed.

Linked imports to WS 4/WS 5.0/GSX from sv2i sources should be disallowed
Linked imports to Symantec LiveState images cannot be read by Workstation 4, Workstation 5.0, or GSX Server 3. Virtual Machine Importer should disallow these linked imports, but does not.

Importing a split Workstation source image residing on a FAT32 filesystem fails
Virtual Machine Importer is unable to import split (2 GB) source disks residing on FAT32 filesystems. Workaround: Copy the source image to an NTFS filesystem before importing it.


THIRD-PARTY FORMATS

Symantec LiveState images containing Windows dynamic disks are not supported
Although the import of Symantec source images containing Windows dynamic disks appears to succeed, the resulting virtual machine may fail to boot.

Virtual Machine Importer fails to detect Microsoft Virtual PC split disks
Virtual Machine Importer is unable to import Microsoft Virtual PC/Virtual Server disks that have been split into 2 GB or 4 GB pieces. Although importing such disks appears to succeed, the resulting virtual machine will not boot.

Virtual Machine Importer fails to detect a live, paused VirtualPC image
Virtual Machine Importer should detect Virtual PC/Virtual Server images that are "live" but paused, and should refuse to import such images. Instead, the import is attempted and fails with an internal error.

"No disk in drive" errors displayed when importing a LiveState image with a Dell DRAC virtual floppy
When importing a LiveState image of a host containing a Dell DRAC virtual floppy drive, Windows might repeatedly display "No disk in drive" error messages.

Virtual Machine Importer fails to import sv2i image when source is specified as a UNC path
The importer is unable to import Symantec LiveState images residing on network shares when the source is specified as a UNC path. Workaround: Mount the share as a drive letter before importing.

Imports of Virtual PC/Virtual Server images containing direct attached disks fail
Virtual Machine Importer should display a more informative error message in this case, but does not.