VMware Converter 3 Beta Refresh Release Notes

Features | Documentation | Knowledge Base | Discussion Forums

Notes on VMware Converter 3 Beta Refresh, Build 33128

Build 32128 is a beta refresh release build of VMware Converter.

The release notes contain the following:

Introduction to VMware Converter 3

VMware Converter provides an easy-to-use, scalable solution for migrations of machines, both physical to virtual and virtual to virtual. Optimized for mass migration, VMware Converter is equally effective for single-machine conversions. With its comprehensive and comprehensible wizards and task manager, VMware Converter imports virtual machines faster, with fewer manual steps required, and fewer source hardware limitations than other methods. Converter can, with its ability to hot clone, import with no downtime on the source physical machine.

VMware Converter combines and expands the functionality available in P2V Assistant and Virtual Machine Importer. It eases interoperability among VMware hosted products (Workstation, VMware Server, and VMware Player), VirtualCenter-managed ESX Server 3.x and 2.5.x, and unmanaged ESX Server 3.x.

What's New

VMware Converter expands the functionality available to users of P2V Assistant and Virtual Machine Importer. Here are some of the new features and capabilities you get when using VMware Converter.

For Users of VMware P2V Assistant
In moving from P2V Assistant to VMware Converter, you see more options and abilities in migrating physical machines, along with the new ability to migrate virtual machines too.

  • A single, central management console to easily deploy, manage, and schedule conversions without the need for a Helper virtual machine.
  • Higher scalability supports multiple simultaneous conversions (Enterprise Edition).
  • New hot cloning functionality for both local and remote source physical machines (no need to reboot Windows 2003 and Windows XP source machines).
  • Broader hardware support for physical machines.
  • Custom tool for adding additional Windows drivers to the Converter Boot CD ISO image.
  • Remote cloning removes the need to walk to and physically interact with each physical machine.
  • Supports cloning a wide variety of Windows operating system platforms. See Supported Guest Operating Systems.
  • Supports migration of hosted VMware virtual machines disk formats (VMware Player, VMware Workstation, VMware GSX Server, and VMware Server) across all VMware virtual machine platforms.
  • Supports conversion of third-party disk image formats such as Microsoft Virtual PC, Microsoft Virtual Server, Symantec Backup Exec System Recovery, and Norton Ghost 9 (or higher).
  • Faster conversion speeds by means of sector-based snapshot cloning.
  • Dramatically reduced number of manual steps for conversion.

For Users of VMware Virtual Machine Importer
In moving from Virtual Machine Importer to VMware Converter, you see more options and abilities in migrating virtual machines, along with the new ability to convert physical machines.

  • A single, central management console to easily deploy, manage, and schedule conversions.
  • Higher scalability supports multiple simultaneous conversions (Enterprise Edition).
  • Local and remote hot cloning of physical machines provides live migrations with zero server downtime for the source machine.
  • Image customization feature allows modification of the virtual machine's guest operating system properties after the conversion.

Help and Feedback

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

Installation Notes

Uninstalling VMware Converter 3 Beta 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.


VMware Converter 3 Beta can be installed on the following platforms:

  • Windows XP Professional
  • Windows 2003 Server
  • Windows 2000 Professional
  • Windows 2000 Server
  • Windows NT SP4+ (IE5 or higher required)

All target operating systems should have the latest patches available from Microsoft as of the release of this product.


VMware Converter 3 Beta supports the following sources and destinations:

 Import from Physical Machines
 Import from Various Third-Party Formats and VMware Products
 Export to a Virtual Machine for
VMware Workstation and Datacenter Products
  • VMware Converter can hot clone and reconfigure any local or remote physical machine running an operating system noted in Platforms
  • VMware Converter Boot CD can be started from, and clone, local machines outfitted with storage controllers and network adapters that Microsoft lists as supported in Windows 2003
  • Microsoft Virtual PC (version 7 and higher)
  • Microsoft Virtual Server (any version)
  • 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.x)
  • VMware ESX Server 3.x
  • VMware ESX Server 3.x (when managed by VirtualCenter 2.x)
  • VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)
  • VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x, ESX Server 2.5.x)2
  • VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)3
  • VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)
  • VMware ESX Server 3.x (when managed by VirtualCenter 2.x)
  • VMware ESX Server 3.x
Not Supported:
  • VMware ESX Server 2.5.x when managed by VirtualCenter 1.x
  • VMware ESX Server 2.5.x unmanaged

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. For ESX Server 2.5.x the .vmdk files must be imported using the vmkfstools utility.

3. 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 Converter 3 Beta:

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

Support for the following guest operating systems is Experimental. VMware Converter 3 Beta 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 Converter 3 Beta release contains the following known issues:


Converter fails when reconfiguring a Microsoft Windows 2000 SP4 virtual machine
VMware Converter cannot successfully reconfigure a Windows 2000 SP4 virtual machine, failing with one of the following error messages in the vmware-p2v log file:

could not locate file: winnt\$ntupdaterolluppackuninstall$\scsiport.sys
Task failed: P2VError HOTFIX_FILE_NOT_FOUND()

Task failed: P2VError UNKNOWN_METHOD_FAULT(sysimage.fault.ReconfigFault)

The converted virtual machine has a bad version of scsiport.sys '5.0.2195.7017' copied over from the source machine. You need to inject a correct version of the same driver into the virtual machine before re-running reconfiguration on it.

  1. Attach the converted virtual machine's system disk to another Windows 2000 SP4 virtual machine—a "helper virtual machine"—and boot the helper virtual machine using its own operating system disk. This enables you to access the converted virtual machine's contents from another virtual machine.

  2. If system32\$ntupdaterolluppackuninstall$\scsiport.sys exists in the attached disk with a version different from the version shown above, then copy scsiport.sys to the system32\drivers location on the same attached disk and shut down the helper virtual machine.


    If the system32\$ntupdaterolluppackuninstall$ directory does not exist in the attached disk, copy the scsiport.sys driver from the system32\drivers folder on the helper virtual machine disk to the attached disk's system32\drivers location, provided the helper virtual machine's scsiport.sys version is different from the one described above. Shut down the helper virtual machine.

  3. Detach the attached converted virtual machine's disk from the helper Windows 2000 SP4 virtual machine, and re-run reconfiguration on it by choosing the "Configure Machine" option from the Converter.

Alternatively, you can install Update Rollup 1 for Microsoft Windows 2000 SP4-v2 from the Microsoft website http://support.microsoft.com/kb/904374/ on your source machine and then use VMware Converter to convert it to a virtual machine.

The Next button is disabled on the wizard's Microsoft Windows NT SMP Reconfiguration page
The Converter wizard shows a disabled Next button on the "Windows NT SMP Reconfiguration" wizard page even after you have given the location of the required listed files by selecting "Have Disk."
Workaround: Delete the %temp%\VMConverterCacheDir\ contents and go through the wizard again.
%temp% is set by your environment.

Manual cleanup required of some Converter Agent files from remote source physical machine
In some cases, the automatic cleanup of Converter Agent files from the system on which it ran is incomplete. If there are vmware-ufad-p2v-XXXXX subdirectories remaining under %SystemRoot% on the remote source physical machine after completion of the import (either successful or failed), automatic cleanup was not totally successful, and might cause future import attempts to fail. To clean up manually (recommended), follow these steps:

  1. Launch regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
  2. Remove the stcp2v30 key
  3. Remove the vstor2-p2v30 key
  4. Remove all vmware-ufad-p2v-XXXXX keys
  5. Remove all courier-XXXXX keys
  6. Reboot
  7. Under %SystemRoot%\system32, remove all vmware-ufad-p2v-XXXXX subdirectories

Converter is unresponsive at startup if a task remaining from an earlier build of the software is already in the task list
If a user installs a build of VMware Converter after uninstalling an earlier build, the application is unresponsive at startup if a task from that earlier build is already in the task list by virtue of remaining in the jobs folder. To delete the old task, follow these steps:

  1. Go to %APPDATA%\VMware\p2v30\jobs
  2. Delete all files
  3. Launch VMware Converter

The active volume and the default system volume must be selected for hot cloning
In setting up a hot clone of a physical machine, be sure its active volume and its default system volume are selected on the wizard's Source Data page. Otherwise the task will fail after reaching the 100% status when you have Converter run it.

Browse disabled after an invalid location is selected for the destination
When a user clicks OK on the error message for selecting an invalid location for the destination virtual machine, and returns to the VM Name & Location page of the wizard, fields and the browse button are disabled, preventing the user from entering a correct location. Workaround:

  1. Click Back on the VM Name & Location page to return to the previous page
  2. Click Next to return to the page
    The fields are still disabled, but the Browse button is now available
  3. Click Browse and choose the correct destination
  4. Click Next, then click Back to verify everything is no longer disabled
  5. Continue

Unable to select sysprep file location during customization because of blank file browser
During a cold clone, clicking the Browse button for "Location of Sysprep Files" on the Computer Information page results in a gray, blank file browser. To customize during cold cloning, you must map the network and manually key in the path. Map a network drive under Administration > Configure Static IP Address and enter the field directly into the text box without using the Browse functionality.

Converter does not import Windows NT 4 with mirrored/striped volumes
Converter is unable to recognize logical devices in Windows NT 4 that span multiple drives. This includes striped and mirrored volumes.

Source with mixed IDE and SCSI disks might not produce a bootable virtual machine
A source machine with both SCSI and IDE disks has the IDE disks attached to the end of the disk list. If the source machine boots from an IDE disk, the target virtual machine created by Converter boots from the wrong disk because a VMware virtual machine looks for the first disk in the disk list. Workaround:

  1. Boot the imported virtual machine and press F2 to enter the BIOS
  2. Go to the Boot menu
  3. Highlight the Hard Drive row and press Enter
  4. Change the boot order of the disks so that the system disk is first
  5. Continue

In trying to import to a FAT32 drive, Converter fails with a local physical source that has the Allocate all disk space option selected
When you store an image on a network drive, make sure that the drive is formatted with NTFS.

Volume-based importing will not work if the source image has more than four volumes on a single disk
Converter cannot import VMware or third-party images that have more than four volumes on a single disk. Use disk-based cloning to import these images. Volume-based importing will work, however, if the more than four volumes are distributed across multiple disks. In addition, if the source has more than four volumes on a single disk, you can use volume-based importing if you select four or fewer volumes from that disk.


Converter import fails when ESX Server connection limit is saturated
When Converter attempts to import to a destination ESX Server that has reached its connection limit, the Converter import task fails at the outset. Disconnect any unneeded VI Clients from the ESX Server and try again.

Importing an ESX Server 2.5.x template virtual machine fails
Currently, attempting to import a template fails with an Unknown error returned by Ufad message. The workaround is to mark the template as a virtual machine, import the virtual machine with Converter, and then mark it as a template again after the import.

Importing to an ESX Server requires more space than the sum of the virtual machine's disks
In order to import to an ESX Server 3.x destination, there must be enough space for the virtual machine and its disks, plus enough extra space to equal a second copy of the largest of those disks. This is because of an incorrect calculation of free space needed. Although the extra free space is required, the space is not actually used.


Entering a local path for destination standalone virtual machine during cold cloning results in an error message
While cold cloning to a standalone virtual machine as a destination, if you enter a local path for the destination on the wizard's VM Name & Folder page, you get an error message stating "Either the destination folder could not be found, or (reconfig-only) the target VM could not be found." Workaround: Enter the UNC path for the destination.

The wizard's Source Data page does not display Dynamic volume's label
When importing a standalone virtual machine as the source, if you use the "Select volumes and resize to save or add space" option, the volume label for a Dynamic volume does not appear in the Volume column.


User cannot create a task if three tasks are already running concurrently
Do no more than three tasks at a time.

The Details View is not refreshed when a user uses the keyboard to scroll through tasks in the Task List
If you use the keyboard up and down arrow keys to move between tasks in the Task List of the Task View, the information in the Details View section of the window is not refreshed for each task. Workaround: Use the mouse to move between tasks in the Task List.


Import of an .sv2i image from a local FAT32 drive fails with "Unable to determine guest operating system"
Currently, importing an .sv2i image works only if it is taken from a local system partitioned with NTFS.