CAUTION: During cloning of powered on Linux machines, Converter Standalone 5.1.1 preserves the following source file systems on the destination: ext2, ext3, ext4, reiserfs, and vfat. All other source file systems are converted into ext3 file systems on the destination virtual machine.

For more information about the operating systems supported by Converter Standalone and other system requirements, see the VMware vCenter Converter Standalone User's Guide.

Prior Releases of Converter Standalone

Features from prior releases of Converter Standalone are described in the release notes for each release. To view release notes for prior releases of Converter Standalone, click one of the following links:

Known Issues

Installation

You must restart machines that run 64-bit Windows Vista or later before re-installing Converter Standalone
If you uninstall Converter Standalone from a 64-bit Windows Vista, Windows Server 2008, or Windows 7 machine and do not restart it, a subsequent Converter Standalone installation might fail with the following error message: Error 29144. Could not install service Vstor2 MntApi 1.0 Driver (shared). Please reboot and try to install again. Workaround: Restart the Windows Vista, Windows Server 2008, or Windows 7 machine and try installing Converter Standalone again.

Converter Standalone installer removes Workstation 6.5.x remote agents without notification
When you use Workstation 6.5.x to hot-clone a Windows source machine, Workstation deploys a remote Workstation agent on the source. If you choose to leave the remote agent on that source and then install Converter Standalone on the same machine, the Converter Standalone installer uninstalls that agent without any warning messages.

Users with limited rights cannot install Converter Standalone on Windows
If you are logged in to Windows as a non-administrator user, the following error message is displayed while the InstallShield is extracting files for Converter Standalone installation: Unable to save file:
C:\WINDOWS\Installer\
The system cannot find the path specified.
The error is displayed because limited users do not have the required write permissions. Workaround: Select the %TEMP% directory to extract the installation files:

Click OK in the error message. A Save As dialog box appears.

Browse to the Temp folder of the current user (for example, C:\Documents and Settings\"username"\Local Settings\Temp) and click OK.

NOTE: You still need to log in as an administrator to install Converter Standalone.

You cannot install vCenter Converter 4.2.1 on the same machine where you have already installed Converter Standalone 5.1
If you install Converter Standalone 5.1 and then install vCenter Converter 4.2.1 server on the same machine, downloading the vCenter Converter 4.2.1 plug-in from vSphere Client fails. Workaround: First install vCenter Converter 4.2.1 and then install Converter Standalone 5.1.

The confirmation dialog when upgrading from Converter Standalone 3.x to Converter Standalone 5.1 is missing
When you install Converter Standalone 5.1 on a machine where Converter Standalone 3.x is installed, the installation wizard does not ask for upgrade confirmation.

General

A running P2V conversion job fails if you create a new conversion job for the same Windows source machine and use a different port to deploy the Converter Standalone agent
If, while running a P2V conversion job, you start creating another conversion job for the same powered on Windows source machine, and specify a port for the connection, Converter Standalone deploys the Converter Standalone agent using the port you specified. If the connection port is different from the one that is being used for the already running conversion job, both jobs fail. The following error message appears in the Job summary tab for the first conversion job: FAILED: A general system error occurred: No connection could be made because the target machine actively refused it. The following error message appears in the Job summary tab for the second conversion job: FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754774 (0x80042316).

You cannot copy running conversion or configuration jobs
If you open the Copy As New wizard for a running configuration or conversion job when the source is a virtual machine or a backup image and you click Next, the wizard displays the error message Unable to obtain hardware information for the selected machine. Workaround: Wait for the job to complete before selecting Copy as New in its pop-up menu.

Linked Cloning of source images greater than 2GB to a network share that does not support large files fails
Creating linked clones from source images that are larger than 2GB to a network share that does not support large files (for example, to a Linux SMB share) fails. Converter Standalone does not split the source files into smaller chunks. If the source is larger than the supported file size on the destination, the conversion tasks fails.

Conversions of vSphere virtual machine sources with 15 or more disks to any ESX destination managed by VirtualCenter 2.5 fail
If you convert a virtual machine source that resides on an ESX 3.5 host to an ESX 3.5 destination managed by VirtualCenter 2.5, and the source machine has 15 or more VMDK files, the conversion job fails with the following error message in Converter Standalone logs: FAILED: agent.internal.fault.NfcConnectionFault.summaryWorkaround:

Convert the source machine to a hosted virtual machine destination, such as Workstation.

Convert the resulting virtual machine to the ESX managed by VirtualCenter where you want it to reside.

Creating a conversion job to convert a standalone VMware source with a VMDK file greater than 2GB from a network share that does not support large files, fails
If you select a standalone virtual machine source with VMDK file greater than 2GB residing on a remote network location that does not support large files (for example, Linux SMB share), the following error message appears in the Converter wizard on clicking Next or View source details: Unable to obtain hardware information for the selected machine. Workaround: Map the network shared folder to the machine where Converter Standalone runs, and select the source from there.

Converter Standalone cannot detect the power state of VMware Workstation or other VMware hosted source virtual machines if they are located on a read-only network share
If the source machine is a Workstation or another VMware hosted source and is located on a network share with read-only permissions, Converter Standalone cannot detect if the source is powered on or suspended. This might lead to data inconsistency on the destination machine if changes are made to the powered on source virtual machine during conversion. Workarounds:

Verify that the source virtual machine is powered off prior to conversion.

Provide write privileges to the network share where the source virtual machine resides.

Task progress is not shown when converting a virtual machine that is larger than 1TB
Converter Standalone does not display the progress of conversion tasks if the source virtual machine is larger than 1TB. Conversion tasks are completed successfully, but the user cannot monitor their progress. Workaround: You can monitor the disk performance of the destination ESX host to check if tasks are running properly.

Conversion jobs from and to ESX hosts that are not connected to vCenter Servers fail if the number of disks on the source machine is more than nine
When converting a source machine that has more than nine disks, conversion fails with the following error in the log file: Error on logout (ignored): Operation timed out
SSLStreamImpl::BIORead (3BBA4E8) timed out.
The error is due to the limited number of NFC connections that can be established to ESX hosts that are not connected to vCenter Servers. Workaround: Connect to the destination ESX host through a vCenter Server. In this case, the number of source disks is limited to 27 for ESX and to 23 for ESXi hosts.

Converting source volumes with unrecognized file systems might prevent the destination virtual machines from starting
While you are setting up a volume-based cloning task in one of the Converter Standalone wizards, the volume name might be missing in some rows of the Source Volumes tab. This means that Converter Standalone does not recognize the file system on those volumes. The destination virtual machine that is created as a result of such a conversion task might fail to start up. Nevertheless, Converter Standalone copies the source volume data to the destination using block-level copying. Workaround: configure the destination virtual machine after the conversion.

Converting standalone VMware sources with a VMDK file greater than 2GB to a hosted destination that resides on a network share that does not support large files, fails
If you select a standalone virtual machine source with VMDK file greater than 2GB and try to convert it to hosted destination residing on a remote network location that does not support large files (for example, Linux SMB or NFS share), the conversion job might fail with one of following error messages:

Unable to connect to the virtual disk

Remote server closed connection after 0 response bytes read

An error occurred during an operation on a virtual disk

.

If conversion is successful, the following error message related to the VMDK file might appear when you power on the destination virtual machine: Internal Inconsistency errorsWorkaround:

In the main application window of Converter Standalone, right-click the failed job and select Copy As New...

Go to the Options page and select Data to Copy.

In the Data to Copy pane, select the volumes to copy and click Advanced.

On the Destination layout tab, select 2GB Split not pre-allocated or 2GB Split pre-allocated as the destination disk type.

Click Next to view a summary of the conversion job.

On the Ready to Complete page, click Finish to resubmit the job.

Converter Standalone is unable to detect the system volume if it resides on a SCSI disk and IDE disks are present in the source machine
On source machines with SCSI and IDE disks, Converter is unable to detect the system volume if the system volume resides on a SCSI disk. Converter only checks the first IDE disk in such configurations.

If the hardware configuration of the source machine is modified while the Conversion wizard is open, you need to restart the conversion wizard if you want to view correct source details
Source machine details are retrieved per wizard session, as this is a time-consuming process. If some changes occur on the source machine (such as adding memory or hard drives) after this information is retrieved, the Conversion wizard does not show information about the changes. Workaround: Restart the conversion wizard.

Timeout on SSL handshake when converting over a WAN link
Converter Standalone does not support conversion over a WAN. When trying to perform a conversion over a WAN link, you might experience an SSL timeout because the timeout for SSL handshakes is two minutes. Workaround:

To avoid the two-minute handshake, perform a conversion to a hosted destination machine (for example, Workstation) in the same LAN.

Copy the temporary virtual machine and send it over the WAN to the remote site.
If the intended destination is a Workstation virtual machine, this completes the process.

If the intended destination is ESX, import the Workstation virtual machine to the ESX server.

User Account Control (UAC) prevents installing Converter Standalone agent if you are not using the default Administrator account to connect to a powered on source machine
If you are setting up a task to convert a powered on source machine that runs Windows Server 2008, Windows Vista, or Windows 7 and you use a non-default Administrator account to log in to the source machine, the following error message might appear when you try to install Converter Standalone agent on the source machine: Insufficient permissions to connect to xxxxxxx. Here xxxxxxx is the IP address of the source machine.
This is because Converter Standalone server cannot install Converter Standalone agent when UAC is enabled and you are logged in to the source as non-default Administrator user. Workaround: Disable the UAC on the source machine before you start the Conversion wizard. You can search the Microsoft Web site for procedures on disabling the UAC depending on the source operating system.

The Reconfigure Virtual Machine wizard does not display correctly the vDS port group name
When you reconfigure a virtual machine that uses dvSwitch and you navigate to the Network interface settings pane, the Network name text box does not display the name of the dvSwitch after the port group name. Only port group is displayed instead.

The reported network transfer rate might not be correct
The reported network transfer rate might be higher than the actual one because of the inherent compression used by the network protocol. This does not affect the network throttling.

Adding a virtual machine to a domain might fail if you specify a fully qualified user name
When configuring a virtual machine, you might not be able to add the virtual machine to a domain if you use a fully qualified user name (DOMAIN_NAME/USER_NAME). Workaround: Specify the user name without including the domain name.

Conversion of a physical machine running Microsoft Windows XP or Windows Server 2003 with a BCD manager (Boot Manager for Windows Vista) and later might fail
If you try to convert a physical machine with a BCD manager, the P2V conversion might fail in the following cases:

Microsoft Windows Vista or later is installed on the source physical machine, which is a dual-boot machine currently running Microsoft Windows XP or Windows Server 2003.

Microsoft Windows Vista or later is installed as a second operating system on the source physical machine and later is removed, but the BCD manager is left on the source machine.

Workaround 1: In case of a dual-boot machine conversion :

Boot the later version of Windows (Windows Vista, Windows Server 2008, or Windows 7).

Perform a physical source conversion.

On the newly created virtual machine, boot a repair CD for the earlier version of Windows (Windows XP or Windows Server 2003).

Remove the BCD manager and revert the operating system to its compatible boot process.

Shut down the virtual machine and reconfigure it by using the Converter Standalone configuration wizard. Now you can boot the machine.

Workaround 2: In case of converting a source machine running Windows XP or Windows Server 2003 with a BCD manager:

On the source machine, boot a repair CD of the corresponding operating system.

Remove the BCD manager and revert the operating system to its compatible boot process.

You cannot perform a P2V conversion without having administrative privileges
If you start the Converter Standalone client under the context of a non-administrative user, you will not able to perform a remote physical to virtual migration. Workaround: Start the Converter Standalone client under the context of a user with administrative privileges.

Conversion fails if the datastore name contains the @ symbol
If the datastore name of the managed source or destination contains "@", the conversion fails. Workaround: Remove the @ symbol from the datastore name and perform the conversion.

Submitting a job might fail with The specified parameter was not correct:"info.owner"message
If Converter Standalone is installed in a client-server mode and you have connected with a Windows domain username by entering the IP address or the host name of the Converter server, submitting a job might fail with The specified parameter was not correct:"info.owner" message. Workaround: Connect either to a local server or by using a local username instead of a domain one.

You might not be able to convert more than nine disks at once
On ESX 3.5 and 4.0, conversion might fail if you try to convert more than nine disks. Workaround: Perform conversion in multiple steps to convert the disks in portions of up to nine. Then, attach all the disks to the target machine.

Windows Sources

[NEW]You can perform only volume-based cloning on the block level for ReFS-formatted volumes
Converter Standalone lets you perform cloning of ReFS-formatted volumes with the following limitations:

You can perform only volume-based cloning on the block level.

You cannot use ReFS-formatted volumes in incremental updates.

You cannot shrink or expand ReFS-formatted volumes.

[NEW]Reconfiguration of Windows virtual machines with multiple active partitions might not complete
For Windows virtual machines with multiple active partitions, Converter Standalone might not recognize the boot partition and might not be able to complete the reconfiguration of the destination virtual machine. In such cases, after the conversion job is 96-98% complete, the conversion job status changes to Failed and an error message appears. For example: FAILED: Unable to find the system volume, reconfiguration is not possible. In the Worker/Agent log this issue is identified by the following statement: [#### warning 'Default'] ERROR: [Mntapi_GetFirstBootDisk] more that *one* active volume found. Current active disk #0, another active disk #1. Workaround 1: Mark all non-boot active partitions on the destination machine as inactive and run configuration on the destination machine.

Boot into Windows Recovery Console on the destination machine.

Run diskpart.exe.
The diskpart command prompt appears.

(Optional) To list the available disks, enter list disk.

Enter select disk <disk_number>.

(Optional) To list the partitions on the selected disk, enter list partition.

Enter select partition <partition_number>.

Enter inactive.

Repeat steps 4-7 to mark another partition as inactive.

Power off the destination machine.

Run Converter Standalone and configure the destination machine.

Workaround 2: Mark all non-boot active partitions on the source machine as inactive and attempt to run the conversion again.

On the source machine, run diskpart.exe.
The diskpart command prompt appears.

(Optional) To list the available disks, enter list disk.

Enter select disk <disk_number>.

(Optional) To list the partitions on the selected disk, enter list partition.

Enter select partition <partition_number>.

Enter inactive.

Repeat steps 2-6 to mark another partition as inactive.

Run Converter Standalone and start the conversion again.

Conversion of a local powered on source machine fails at 1%
If you select This local machine as a conversion source and a Converter Standalone agent from a previous Converter Standalone version is installed on the source machine, the conversion task fails at 1%. The following error message appears in the Status line of the Task progress tab: FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 127 (0x0000007F).
This is because the Converter Standalone installer cannot upgrade previous versions of Converter Standalone agents. Workaround: Manually uninstall Converter Standalone agent from the source machine and create a new conversion task.

Converter Standalone worker process stops responding if you try to copy a configuration job during guest operating system customization
If you right-click a running configuration job and select Copy As New while the destination machine is being customized, Converter Standalone worker process stops responding. Workaround: Wait for the configuration job to complete before you copy it.

Subsequent P2V conversions of remote source machines that run 64-bit Windows Vista or later might fail after a successful conversion
If you convert successfully a remote source machine that runs 64-bit Windows Vista, Windows Server 2008, or Windows 7 operating system and then try converting it again, the conversion fails with the error message Converter Standalone Agent installation failed on x.x.x.x Error code: 1603, where x.x.x.x is the IP address of the source machine.
This error message might occur if automatic uninstall of remote Converter Standalone agent has been enabled during the first successful conversion. Workaround: Restart the remote source machine and try running the conversion task again.

Converter Standalone does not preserve disabled network adapters during conversion of physical machine sources that run on Windows
During P2V conversion of Windows source machines, Converter Standalone does not detect disabled network adapters on the source and does not preserve them on the destination virtual machine. Workaround: On the Options page of the Converter Standalone wizard, click Networks to add network adapters to the destination virtual machine.

Microsoft Windows Vista reboots repeatedly after customization
Providing wrong customization information might cause the destination virtual machine to reboot repeatedly if the source operating system is Microsoft Windows Vista. During conversion or configuration, if you choose to customize Microsoft Windows Vista and provide wrong customization information, for example an invalid serial key, the customized destination reboots repeatedly. This is a known issue with Microsoft Windows Vista. Workaround: Make sure that the provided customization information is valid.

Converter Standalone does not support cloning powered on Windows Server 2008 sources with FAT/FAT32 volume file system
VSS under Windows Server 2008 does not support FAT/FAT32. Trying to convert a FAT/FAT32 volume causes the conversion task to fail. Workaround: Deselect all FAT/FAT32 volumes on the Options page of the Conversion wizard.

Converter Standalone remote agent does not notify the user about Converter 3.0.x or 4.0.x remote agents that have been installed on the source system during remote hot cloning process
If Converter Standalone is converting a remote machine source that already has a remote agent from Converter version 3.0.x or 4.0.x, it uninstalls the old remote agent without issuing a notification or warning message. This prevents older Converter versions from converting this source machine later.

Previous Converter versions cannot convert source machines that have Converter Standalone 5.1 agent installed on them
Converter Standalone 5.1 agent is deployed on the source machine during conversion. If Converter Standalone 5.1 agent is not uninstalled after the conversion, older Converter versions cannot deploy their agents on top of the newer Converter Standalone agent version. Therefore, you cannot use previous Converter versions to convert sources that have already been converted with Converter Standalone 5.1. Workaround: Uninstall Converter Standalone 5.1 agent before trying to convert the source with an older Converter version.

Stopping Converter Standalone processes during file-level cloning might cause the machine that runs the Converter Standalone Server service to restart
During file-level cloning of source systems that run Windows XP or Windows Server 2003, if any of the following Converter Standalone process is forcibly stopped, the machine on which the stopped process was running might automatically reboot.

VMware Converter Standalone Integrated Worker

VMware Converter Standalone Integrated Agent

This behavior is not consistent and depends on the Windows version and patch level.

Converter Standalone does not change PIC HAL to APIC HAL during conversion of Windows source machines
If the source to convert is running a Programmable Interrupt Controller (PIC) HAL, Converter Standalone does not change the PIC HAL to an Advanced Programmable Interrupt Controller (APIC) HAL in the destination virtual machine. As a result, the destination virtual machine might not boot or might fail to perform as expected. To find out which HAL is running, go to Windows Device Manager and select Computer in the list of devices. If it displays Standard PC or Advanced Configuration and Power Interface (ACPI) PC, you are running a PIC HAL. Workaround: VMware virtual machines are APIC computers. If your source computer is a PIC computer that runs a PIC HAL, you must update the HAL in the destination virtual machine to APIC HAL after the conversion. For more information on configuring the correct HAL, check the Microsoft Web site HAL options after Windows XP or Windows Server 2003 Setup. Note: Microsoft does not support running a PIC HAL on an APIC computer. If your source is an APIC computer running a PIC HAL, you must configure the correct HAL on the source machine before starting the conversion.

Owner name and organization are not displayed properly after customizing the guest operating system
After customizing the guest operating system, Unicode characters used for owner name and organization on the Computer Information page do not appear the way they were set in the Conversion or the Configuration wizard.
For all Windows operating systems except Windows Vista, customization parameters such as user name and organization must use characters only from the local encoding of the default user profile of the guest. For example, you can use Japanese characters for the user name only on a guest whose default user profile's local encoding is set to Japanese. These restrictions do not apply to Windows Vista guests because Windows Vista uses a UTF-8 encoded XML file to store the Microsoft sysprep parameters. Earlier versions of Windows use the sysprep.inf file, and the Microsoft Windows mini-setup process reads that file in the local encoding only. Workaround: Either avoid Unicode characters when assigning owner name and organization name for the destination virtual machine, or use the workaround described at: http://support.microsoft.com/kb/310441/.

Converter can convert FAT/FAT32 volumes during hot cloning only if the source machine has at least one NTFS volume
For source machines running under Windows versions earlier than Windows Server 2008, VSS can take snapshots of FAT/FAT32 volumes only if the source machine has at least one NTFS volume. For all operating systems that support volume-based cloning, you need at least one NTFS volume for VSS to work.

In the Computer Management window, select Services and Applications > Services on the left.

In the list on the right, double-click VMware Converter Standalone Agent.

Click Start to start the process.

Click Apply followed by OK.

The source virtual machine does not have the appropriate drivers
The following error message appears in the log file when reconfiguration fails because the appropriate drivers are missing from the source operating system: Unable to find symmpi.sys in the specified CAB files
This is usually observed in Windows Server 2003 SP1. Workaround:

Back up the virtual machine created during the failed conversion.

Attach the VMDK file containing the system folder to another Windows Server 2003 virtual machine.

Replace the WINDOWS\Driver Cache\i386\driver.cab file in the destination virtual machine with a version of the driver.cab file that includes the missing driver from the helper virtual machine.

Detach the VMDK file from the helper virtual machine and run the Configure Machine wizard on the destination virtual machine.

Sysprep deletes drive letter mappings during customization
If you choose customization options and the destination virtual machine fails at a Please Wait screen after
the second sysprep reboot, you need to rerun the conversion task without customization. This issue occurs because of
a problem with Microsoft sysprep, which deletes the drive letter mappings, preventing access to certain files.

You cannot import a Windows source with "signature()" in the boot.ini file
You cannot import a Window source with "signature()" in the boot.ini file. If you import a Windows live source with "signature()" in the boot.ini file, and try to reconfigure and convert it, the reconfiguration fails and this results in a conversion error. If you try to convert the source without reconfiguration, the conversion succeeds but the destination cannot boot. For more information on "signature()" go to http://support.microsoft.com/kb/227704.

Linux Sources

[NEW]P2V conversions of SLES 9 sources cannot complete, if the root directory is located on an LVM disk
When you select to convert a physical SLES 9 source, Converter Standalone cannot complete the conversion if the root directory is located on an LVM disk. After the conversion job is 99% complete, the job status changes to Failed and the following entry is added to the log: FAILED: An error occurred during the conversion: 'Failed to restore original lvm in initrd image: /usr/lib/vmware-converter/restoreLvmInInitrd.sh failed with return code: 1, and message: * Unpacking initrd image /mnt/p2v-src-root//boot/initrd cpio: unsupported cpio format, use newc or crc ERROR: Unable to unpack initrd image /mnt/p2v-src-root//boot/initrd 'Workaround: Convert the LVM disk to a basic disk.

On the Options page of the Conversion wizard, click Data to copy in the options list.

Click Advanced and select the Destination layout tab.

Select the volume that contains the root directory and click To basic.

Virtual machines converted from Hyper-V virtual machine sources that run SLES 11 do not start up after conversion
If you select to convert a powered off virtual machine that resides on a Hyper-V Server, the resulting virtual machine cannot start up after the conversion if the guest operating system of the source machine is SLES 11. This is because the SLES boot loader uses source disk IDs, and disk IDs are changed during the conversion process. Workarounds:

Power on the source virtual machine on the Hyper-V Server and follow the procedure for converting powered on sources.

After the conversion, start up the destination virtual machine using the SLES 11 Installation DVD and select Repair installed system in the list of options. Follow the on-screen instructions to fix the boot loader and the fstab entries.

X Server might fail to start in destination virtual machines converted from sources that run Linux
When the destination virtual machine starts, X server might fail to start with an error Fatal X server Error. This is due to incompatibility issues between the display driver used in the Linux source and the display adapter of the destination VMware virtual machine. Workarounds:

Install VMware Tools on the destination virtual machine.

configure the X server on the destination virtual machine to change the refresh rate and the display resolution.

Linked cloning of standalone VMware sources to Linux SMB shared destination fails
Linked cloning tasks of VMware standalone sources to SMB shared destinations that run on Linux fail with the following error: converter.fault.FileIOFault.

The number of LVM logical volumes per volume group is limited to 12 for powered on Linux sources
During the conversion of powered on Linux machines, Converter Standalone converts LVM volume groups into new disks on the destination virtual machine. The number of LVM logical volumes on a source LVM volume group cannot exceed 12. Workaround: Move volumes out of the new disk to other destination disks:

On the Destination layout tab, select a volume to move and click Move Up or Move Down until it is moved to the destination disk.
You can move volumes between disks only if they are not Active /boot or System / volumes.

(Optional) To create a new destination disk, click Add Disk.

By default, the Linux P2V helper virtual machine is powered off when the conversion job finishesWorkaround: Manually disable this option in the converter-worker.xml file.

On the machine where Converter Standalone server runs, browse to the converter-worker.xml file in the following location %ALLUSERSPROFILE%\Application Data\VMware\VMware Converter Standalone\.

Open the converter-worker.xml file in a text editor and change the powerOffHelperVm flag from true to false.

To restart Converter Standalone worker:
Reboot the system or open the Services section in the Microsoft Management Console, find the VMware Converter Worker service and restart it.

Note: Care should be taken when this option is enabled and the helper VM network is configured to use a static IP address. After the conversion, the helper VM retains the statically configured IP because it is still running. Thus any subsequent Linux P2V jobs cannot use the same static IP until this helper VM is powered off, or at least has its network interface disabled.
Disabling the powerOffHelperVm flag is useful when the useSourcePasswordInHelperVm Converter Standalone worker flag is enabled. This allows users to log in to the helper virtual machine after conversion.

Source volumes on top of volume managers other than LVM are not recognized during conversion of powered on Linux machines
Converter Standalone recognizes only managed source volumes that run on the LVM volume manager. Other volume managers, including but not limited to Veritas Volume Manager (VxVM), are not recognized.

Converter Standalone does not recognize source volumes that reside on Linux Software RAID configurations
During cloning of powered on Linux machines, Converter Standalone does not recognize source volumes that are part of a Software RAID configuration (also referred to as multiple disk, or MD, configurations).

LILO boot loader is not supported for Linux sources
You can convert powered on machines that run Linux only if GRUB is installed as the boot loader on the source.

By default, Converter Standalone has a 20 minute timeout when waiting for the helper virtual machine to start up during Linux P2V conversion
This might cause a Linux P2V conversion task to fail due to connection timeout. Workaround: Extend the timeout period (in milliseconds) by modifying the linuxP2VBootTimeout flag in the converter-worker.xml file.

On the machine where Converter Standalone server runs, browse to the converter-worker.xml file in the following location %ALLUSERSPROFILE%\Application Data\VMware\VMware Converter Standalone\.

Open the converter-worker.xml file in a text editor and replace the default value for linuxP2VBootTimeout with the necessary timeout value in milliseconds. Note: The timeout value is measured in milliseconds. To specify the timeout in minutes, multiply the number of minutes by 60000 and use that value.

To restart Converter Standalone worker:
Reboot the system or open the Services section in the Microsoft Management Console, find the VMware Converter Worker service and restart it.

Sparse files are not preserved during conversion of powered on source machines that run Linux
By default, Converter Standalone does not preserve sparse files on the source machine during Linux P2V conversion. If you have large sparse files on the source, they are created as non-sparse on the destination virtual machine. This renders the used space on the destination file system larger than that on the source machine. This might also cause the conversion task to fail with a timeout error. Workaround: Manually enable preserving sparse files during Linux conversions by modifying the keepsake flag in the converter-worker.xml file.

On the machine where Converter Standalone server runs, browse to the converter-worker.xml file in the following location %ALLUSERSPROFILE%\Application Data\VMware\VMware Converter Standalone\.

Open the converter-worker.xml file in a text editor and change the keepsake flag from false to true.

To restart Converter Standalone worker:
Reboot the system or open the Services section in the Microsoft Management Console, find the VMware Converter Worker service and restart it.

Destination virtual machine might not boot if you change the disk controller type while converting a Linux virtual machine
In Linux virtual machines, the root device can be defined using the block device name (such as /dev/sda1) in /boot/grub/grub.conf, /boot/grub/menu.lst, or /etc/fstab. If you change the disk controller type while converting the virtual machine, the destination virtual machine might not boot. This is because the root device now has a different name (for example, it might have been changed to /dev/hda1). Workaround: Configure the destination virtual machine manually. At the minimum, change the root device name to reflect its new name in the destination virtual machine. To make your system more robust, use the volume label or UUID instead of the block device name.

During conversion of powered on Linux machines, Converter Standalone does not recognize Linux source volumes if they are mapped directly on a hard diskWorkaround: Linux source volumes that are not managed by LVM must be located in a partition so that Converter Standalone can recognize them during cloning of powered on Linux sources.

Linux P2V jobs on ESX 5.0 target hosts fail if the name of the virtual machine is not in ASCII symbols or in the Windows current system locale
If the target host is ESX 5.0, the name of the virtual machine must be in ASCII or in the Windows current system locale, otherwise the helper machine cannot be connected and the Linux P2V conversion fails. Workaround: Before the conversion, enter the name of the virtual machine by using ASCII symbols. After the conversion is complete, you can rename the virtual machine.

Third-Party Formats

Virtual machines created from Acronis images that have dynamic volumes do not start up after the conversion
Some Acronis True Image images of Windows Vista, Windows Server 2008, or Windows 7 are not correctly configured and do not start up after the conversion. The problem occurs when the system or the active disk is located on a dynamic volume in the source. Workaround:

Create a new virtual machine using the vSphere Client.

Use the Acronis True Image software to restore the image inside the new virtual machine.

Limitations when converting third-party images
You can use Converter Standalone to convert third-party virtual machines, system images, and backup images with the following limitations:

Backups of systems with dynamic disks are not supported (ShadowProtect and Backup Exec System Recovery).

All images for the backup of a machine must be in a single folder that contains no other images (ShadowProtect and Backup Exec System Recovery).

For incremental images, up to 16 incremental backups are supported (ShadowProtect and Backup Exec System Recovery).

Images of systems with logical volumes are not supported if the logical drive is also a system or active volume (only for ShadowProtect sources).

For volume-based cloning of Acronis and StorageCraft, all volumes in the disk before the active and system volumes must be backed up. For example, if a disk has 4 partitions, 1-4, with partition 2 as the active volume and partition 3 as the system volume, the backup must include volumes 1 through 3 (ShadowProtect and Backup Exec System Recovery).

Virtual machines from Macintosh versions of Virtual PC are not supported.

Older versions of VMware products have limited support of newer operating systems. For example, ESX 3.5 does not support Windows 7. The converted source operating system must be supported for the destination VMware platform. For a list of supported systems, see the Guest Operating System Installation Guide.

Separate backup images should be stored in separate folders
Storing more than one third-party backup in a single folder results in a failed migration. Workaround: Place each backup in its own folder before using Converter Standalone to convert an image.

Converting Windows Server 2008 images with more than one disk results in all disks being offline except the disk on which the operating system exists
If you are converting a Windows Server 2008 Enterprise Edition or Datacenter Edition virtual machine with multiple disks, some of the disks might remain offline. This is because Windows Server 2008 has a new SAN policy that determines whether a newly discovered disk is brought online or remains offline.
For additional information about the new SAN policy, go to the Microsoft Knowledge Base.

SDK Release Notes

Converter Standalone SDK 5.1

The VMware vCenter Converter Standalone API provides language-neutral interfaces to the Converter Standalone server management framework.
The Converter Standalone SDK is a ZIP file that contains the following items.

Sample code demonstrating common use cases for programmatically managing Converter Standalone server. The sample code includes Java and C# source code files. See the respective Readme files (readme_java.htm and readme_dotnet.htm ) for information about building and using the samples.

The WSDL that defines the API available on Converter server.

Batch files and shell scripts to automate the process of generating client-side stubs, and for rebuilding the sample applications.
For C# developers, the Microsoft Visual Studio project files (.sln) have been included.