VMware

VMware Converter 3 Release Notes

Features | Documentation | Knowledge Base | Discussion Forums

Notes on VMware Converter 3.0.3 | 5/6/2008 | Build 89816

Build 89816 is maintenance release build of VMware Converter.

The release notes contain the following sections:

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 converts virtual machines faster, with fewer manual steps required, and fewer source hardware limitations than other methods. With its ability to perform hot cloning, VMware Converter can convert a virtual machine with no downtime on the source physical machine.

VMware Converter eases interoperability among VMware hosted products (Workstation, VMware Server, VMware Player, and Fusion), unmanaged ESX Server 3.x, ESX Server 3i Embedded, ESX Server 3i Installable, and ESX Server 3.x and 2.5.x, ESX Server 3i Embedded, ESX Server 3i Installable managed by VirtualCenter.

New in Converter 3.0.3

VMware Converter 3.0.3 is a maintenance release of VMware Converter. It has the following enhancements:

  • Contains bug fixes described in Resolved Issues and known issues described in Known Issues
  • Can convert individual volumes on a single physical disk from the source physical machine to separate and independent virtual disks across different datastores
  • Can import as well as create Virtual Appliances in Open Virtual Machine Format (OVF) version 0.9
  • Can remove all System Restore checkpoints in the target virtual machine when doing volume-based cloning
  • Provides full support for Microsoft Vista 32-bit and 64-bit operating systems

New in Converter 3.0.2 Update 1

Version 3.0.2 Update 1 is an update release of VMware Converter. It contains bug fixes described in Resolved Issues and a known issue described in Known Issues. (VMware Converter 3.0.2 Update 1 contains fixes that might not apply to you.)

New in Converter 3.0.2

Version 3.0.2 is a maintenance release of VMware Converter. It contains bug fixes described in Resolved Issues, and also incorporates the following new features:

  • Conversion of VMware hardware version 6 products: Workstation 6.x, VMware ACE 2.x, VMware Fusion 1.x, and VMware Player 2.x
  • Conversion of an additional third-party disk image format: Acronis True Image 9
  • Experimental support for Microsoft Vista 32-bit and 64-bit operating systems
  • Ability to set speed and duplex settings on the network adapter while performing cold cloning migrations, by using the VMware Converter Enterprise Boot CD
  • Support for Symantec Backup Exec System Recovery 7.0

New in Converter 3.0.1

Version 3.0.1 is a maintenance release of VMware Converter. It contains bug fixes described in Resolved Issues, and also incorporates the following new features:

VMware Converter imports VMware Consolidated Backup images
Converter can restore Consolidated Backup images into ESX Server machines, and can import them into VMware standalone virtual machines. Converter supports restoring Consolidated Backup images of any guest operating system type.

VMware Converter imports certain StorageCraft ShadowProtect images
Converter can import ShadowProtect images, with some limitations. These limitations include:

  • Dynamic disks are not supported
  • All images for the backup of a machine should be in a single folder, with no other images placed there
  • For volume-based cloning, all volumes in the disk up to the active and system volumes must have been backed up (For instance: a disk has four partitions, 1 - 4, with partition 2 as the active volume and partition 3 as the system volume. The backup must include 1 through 3)
  • If it is an incremental image, up to 16 incremental backups are supported
  • Images of systems with logical drives are not supported if the default boot (Windows) partition is on a logical drive.

VMware Converter provides an experimental command line interface for migrations
VMware provides p2vTool as a tool for migrating physical and virtual source machines with a command line interface (CLI). Support for this CLI is Experimental. Therefore, users cannot file Support Requests (SRs) to VMware for p2vTool-related issues.

You need an Enterprise license to use p2vTool to migrate machines. The one exception is restoring a VMware Consolidated Backup image; in this case p2vTool can execute the query, verify, import, and postprocess options without needing a license if it detects that the source is a VCB image.

New in Converter 3.0

VMware Converter expands the functionality available to users of P2V Assistant and Virtual Machine Importer. 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. 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.

Installation Notes

The Converter installer uninstalls previously installed versions of Converter such as 3.0.2, 3.0.1, or 3.0 before installing version 3.0.3.

Platforms

You can install VMware Converter 3 on the following platforms:

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

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

Interoperability

VMware Converter 3 supports the following sources and destinations:

 Import from Physical Machines
(Source)
 Import from Various Third-Party Formats and VMware products, including virtual appliances
(Source)
 Export to a Virtual Machine or VMware Virtual Appliance for VMware Workstation and Datacenter Products
(Destination)
  • 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 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, 2
  • StorageCraft ShadowProtect images 2, 4
  • Acronis True Image4
  • VMware OVF virtual appliances5
  • VMware Workstation 6.x virtual machine (compatible with VMware Player 2.x, and VMware Server 1.x)4
  • VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)
  • VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.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 ACE 2.x
  • VMware Fusion 1.x
  • VMware Consolidated Backup images2
  • VMware OVF virtual appliances5
  • VMware Workstation 6.x virtual machine (compatible with VMware Player 2.x, and VMware Server 1.x)4
  • VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)4
  • VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x, ESX Server 2.5.x)3
  • VMware ESX Server 3.x (when managed by VirtualCenter 2.x)
  • VMware ESX Server 3.x
  • VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)
  • VMware ACE 2.x
  • VMware Fusion 1.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 Backup Exec System Recovery (formerly LiveState Recovery) 6.5 and 7.0, LiveState Recovery 3.0 and 6.0, and the Norton Ghost 9, 10, and 12.

2. For conditions and limitations about importing Backup Exec System Recovery, ShadowProtect, and Consolidated Backup images, see chapter 2, "System Requirements," of the VMware Converter User's Manual.

3. Select Workstation 4.x as the destination in the Converter GUI. After the import is complete, use vmkfstools on the target ESX machine to import the resulting Workstation 4.5 virtual machine to ESX 2.5.x.

4. Only Workstation 5.5 and 6.x can power on linked imports of .sv2i images. Workstation 6 is required to power on linked clones of Acronis True Image and StorageCraft ShadowProtect images.

5. OVF supports import and creation of .vmdk images only.


Supported Guest Operating Systems

The following guest operating systems are fully supported by VMware Converter 3:

  • Windows Vista (32-bit and 64-bit)
  • Windows XP Professional (32- bit and 64-bit)
  • Windows 2003 Server (32-bit and 64-bit)
  • Windows 2000 Professional (32-bit)
  • Windows 2000 Server (32-bit)
  • Windows NT 4 SP4+ (32-bit) (IE5 or higher required)

Support for the following guest operating systems is Experimental. VMware Converter 3 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 might 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

Known Issues

This VMware Converter 3 release contains the following known issues:

GENERAL

New Scheduled tasks are not performed after physical to virtual hot cloning of Windows systems
After performing a physical to virtual conversion, the account context of scheduled tasks is not preserved when the system is rebooted and the task associated with a specific user account is started at logon.
Workaround: In Converter 3.0.3, use cold cloning instead of hot cloning to preserve the account context of Windows scheduled tasks in the target virtual machine.

New Remote hot clone of Windows NT4 from a Windows Vista host is not supported
If you try to remote hot clone Windows NT4 from a Windows Vista host, Converter agent deployment might fail with an error message. This conversion scenario is not supported.

New When you resize disks to "Min size" in the Converter wizard, the resulting new disk size is slightly larger
If you hot clone a physical source machine and specify Min size for the source data, the actual disk size created is approximately 10 percent larger than the displayed minimum size.

New Converter does not support Windows NT 4 with fault-tolerant volumes
You cannot import Windows NT 4 with fault-tolerant volumes.

New On a Windows Vista virtual machine that has more than one virtual NIC, some NICs don't capture the static IP addresses when customization is used to set them
If you try to configure static IP settings for more than one NIC on a Vista guest operating system, the settings might not be applied correctly to all NICs.
Workaround: Manually configure the static IP settings.

New Converter quits with an error if VCB image path includes non-ASCII characters
If you specify a VCB image whose path includes non-ASCII characters for target virtual machine names, during import an Unable to determine Guest Operating System error message displays.
Workaround: To avoid this issue, store the VCB image on a path that includes only ASCII characters.

New Task fails for remote Windows source machine when you navigate back and forth in the Conversion wizard
When all of the following circumstances exist, the physical source machine does not reboot:

  • You are remote hot cloning a Windows NT4 or Windows 2000 source machine
  • The agent is installed on the source machine, but the system has not yet been rebooted
  • You change the source selection and change back to the original source before you click Finish in the Conversion wizard
In this scenario, the task fails with a snapshot failure error message. The reboot is necessary to start the snapshot service on the remote source machine so that Converter can take the snapshot of the machine.

New Source virtual machine networks are not reflected in the default networks of the OVF package
When you create an OVF virtual appliance, the networks in the source virtual machine are not reflected in the default networks of the OVF package. Instead, Converter includes one default network, VMNetwork. You can edit the Network section on the virtual appliance Details page to add more networks if required.

New The target virtual machine is not created when performing an OVF export larger than 2GB
Virtual appliances can be very large and might exceed 2GB in size. When choosing a destination for your Virtual Appliance (OVF or OVA), ensure that you use a file system, such as NTFS, that can support large files. FAT file systems do not support files greater than 2GB. If a conversion process fails, an error code = 12 in the log file indicates that you reached this limitation.

New Remote hot cloning limitation with Windows Vista User Account Control
If you are converting a Windows Vista machine and plan to use an Administrator account other than the machine's built-in account, you must turn off User Account Control (UAC) before proceeding with hot cloning.

New Converter quits with an error message if number of volumes on source IDE disks plus the IDE CD-ROMs exceed Workstation IDE slot limit
If you select the option to create a separate disk for each volume and the number of volumes on the source IDE disks combined with the number of IDE CD-ROMs is more than the allowable IDE devices in Workstation, the conversion task fails and Converter issues an error message.
Workaround: If the chosen volumes residing on the IDE disks and the IDE CD-ROMs exceed Workstation IDE device limits, you must deselect some of the volumes residing on the IDE disks during conversion.

New System Restore checkpoints are not removed in target virtual machine
When performing block-level, volume-based cloning of a VMware virtual machine (ESX Server or Workstation), regardless of whether you selected the Remove all System Restore checkpoints option in the Conversion wizard, these checkpoints are not removed in the target virtual machine.
Workaround: In the source virtual machine, grant everyone full control of the System Volume Information folder:

  1. Double-click My Computer and on the menu bar, select Tools > Folder Options > View, and deselect Hide protected operating system files.
  2. Right click each volume you want to clone and select System Volume Information.
  3. Select Properties, click the Security tab and select Add Everyone and select Full Control.
  4. Click OK and proceed with cloning.

New Non-ASCII virtual machine names during cold clone cause Converter to quit with an error message
During cold cloning, if you use non-ASCII characters for target virtual machine names, although it appears that the import is progressing, Converter issues an error message and quits.
Workaround: Use only ASCII characters for virtual machine names when performing a cold clone.

New The "Create a separate disk for each volume" option is not recommended for multi-boot systems
The Create a separate disk for each volume option on the Source Data page of the Conversion wizard does not support multi-boot systems. If you clone a physical or virtual machine that has a multi-boot configuration, every system volume except for the recognized system volume is placed on a new disk. This prevents the target virtual machine from booting into any of the additional system volumes.
Workaround: Deselect additional system volumes so they are not cloned in the target virtual machine.

New End User License Agreement license files are not added to OVF packages
The End User License Agreement addition/removal will not succeed if

  • You edit an OVF creation task after you restart the converter application.
  • You edit an OVF creation task for which you didn't specify an End User License Agreement license, but are specifying one now without restarting the Converter application.
Workaround: Create a new task instead of editing the same task.

New OVA file is overwritten if an .ova file with a specified virtual appliance name already exists
If you are exporting to a virtual appliance with the OVA file option specified, and if an .ova file with a name identical to the destination virtual appliance name specified already exists, an error message is not issued and the existing OVA file is overwritten. If, however, the existing .ova file is read only, the OVA creation task fails.

A linked clone of a VMware virtual machine to a hosted destination fails
A linked clone of a virtual machine that resides on a File Allocation Table (FAT) file system is supported only if its VMDK files are in 2GB split format.

Cannot load a Windows 2000 Virtual PC image on a Windows 2000 Server with SP4 host
The Microsoft Windows system that Converter is installed on must have Microsoft XML Parser (MSXML) 2.6, 3.0 or 4.0 installed to successfully import Virtual PC images.

The source virtual machine does not have the appropriate drivers
A log file error message such as "Unable to find symmpi.sys in the specified CAB files," indicates that reconfiguration failed because the appropriate drivers are not present on the source operating system. This is usually observed in Windows 2003 Server SP1.

Workaround 1:

  1. Set aside the virtual machine created during the failed import.
  2. Attach the VMDK file containing the system folder to another Windows 2003 virtual machine.
  3. Replace the WINDOWS\Driver Cache\i386\driver.cab file in the target virtual machine with a version of the driver.cab file that includes the missing driver from the helper virtual machine.
  4. Detach the VMDK file from the helper virtual machine and run the Configure Machine wizard on the target virtual Machine.
Workaround 2:
  1. Replace the driver.cab file, as mentioned in step 3, in the source virtual and physical machine before the migration.
  2. Rerun the migration.

The CD-ROM device does not work after importing Windows Vista to virtual machines
The CD-ROM device does not work after importing Windows Vista to ESX 3.x or to a Workstation version earlier than VMware Workstation 6. The CD-ROM driver that comes with Windows Vista does not work with the emulated CD-ROM devices in ESX 3.x and Workstation versions earlier than 6. Support for Windows Vista as a guest operating system is experimental for ESX 3.0.x and Workstation 5.x. Vista is fully supported as a guest operating system on Workstation 6. Workstation 4.x and ESX 2.x do not support Vista. For a list of VMware products that have experimental support for Windows Vista, see the Guest Operating System Installation Guide .

Hot clone of Windows Vista fails with permission error
Although you log in as a user with administrative privileges, the clone of Windows Vista operating system fails because of insufficient permission to perform the operation. To perform a hot clone of Windows Vista, you must run VMware Converter as Administrator by right clicking the VMware Converter icon on your desktop and choosing "Run as Administrator."

Installer creates a new vmware-client-config.xml file
The Installer creates a new vmware-client-config.xml file and if you customized the location of logs in the configuration file, that information will be lost.

Network adapter instances are not listed under the Advanced tab in the Network configuration window when using Converter Boot CD for cold cloning
Broadcom's NetXtreme II Ethernet controllers 5706 and 5708 are not listed under the Advanced tab in the Network configuration window. These network adapters are not detected during cold cloning because of limitations in the WinPE operating system. The network device's advanced options are not available, even though network connectivity is provided.

Snapshot fails when cloning an unformatted Windows volume
Vmware Converter does not support hot cloning of a recognized, but unformatted, Windows volume. When doing a hot clone, you must deselect any unformatted volumes.

The target virtual machine is not bootable if the active system volume is not formatted by Microsoft Operating System
When you import a virtual machine by using a volume-based cloning method and the source machine's active system volume is not formatted by Microsoft Operating System, the target virtual machine might not boot up. Workaround: Use disk-based cloning (import all disks and maintain the size option) by running the Converter Boot CD.

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.

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.

Incorrect reboot warning when installing Converter manager only
When installing only the Converter manager, and not the Converter agent, on machines running Windows 2000 or Windows NT operating systems, you do not need to reboot despite the Custom Setup page in the installer warning that you need to.

Sysprep deletes drive letter mappings if your task includes customization
If you choose customization options and the destination virtual machine fails at a "Please Wait" screen after the second, sysprep reboot, you will need to rerun the import without customization. This problem occurs because of a problem with Microsoft's sysprep, which has deleted the drive letter mappings, preventing access to certain files.

After customizing a virtual machine, rebooting it produces an error message that msgina.dll failed to load
See the VMware Knowledge Base article, Error: "Logon User Interface DLL msgina.dll failed to load":
and the Microsoft knowledge base article, "Error Message: User Interface Failure: The Logon User Interface DLL Msgina.dll Failed to Load":

Unable to connect to remote source machine for physical computer on the source login page
During a remote hot clone, if you provide valid credentials for a valid account, then go back and change the credentials to that of another user, you might see this error: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. To be able to change login credentials on the source login page

  1. Open a command window and at the prompt, type


    net use \\<remote host name or IP> \ADMIN$ /delete
    net use \\<remote host name or IP> \IPC$ /delete

  2. Log in again using the new credentials.

Customization is not applied if a virtual machine is manually restarted after running the Configure Machine option
The process for customization occurs in this order:

  1. Customize the virtual machine image with Converter and wait for 100 percent completion.
  2. Power on the virtual machine.
  3. Wait for it to reboot automatically.
  4. Sysprep processes the customizations.
  5. Sysprep reboots the virtual machine.
  6. The Windows operating system loads, and the network configurations occur.
If you manually reboot the virtual machine after step 2, without waiting for it to automatically reboot, the customization process will break. If Windows discovers new hardware and asks you to reboot and you select YES, the customization process will also break. In both scenarios, customization settings are not applied to the virtual machine. You must wait for the machine to automatically reboot twice before the customization settings are applied and you can safely log on.

Unable to remote hot clone a Windows NT virtual machine to a folder inside a network share
When remote hot cloning Windows NT virtual machines, you might have problems importing a virtual machine to a sub-folder under a share. That is, if \\[hostname]\share_name is the network share, remote hot cloning to \\[hostname]\share_name will work, but cloning to \\[hostname]\share_name\sub_folder might not work.

UFAD Service startup is delayed when user logs in to Converter as "Limited User"
UFAD might not start up before Windows ServicesPipeTimeout (30 seconds) expires if you do not log in as Administrator. If the source machine is busy or running slow, the service does not start quickly enough for Windows and UFAD is no longer running. A user with administrator privileges can restart the service manually.

The "Configure Virtual Machine" option should not be used on legacy virtual machines
"Configure Virtual Machine" automatically upgrades the virtual hardware and configuration file version of legacy virtual machines. If you run "Configure Virtual Machine" on a Workstation 4.x or GSX Server 3.x virtual machine, the hardware version is irreversibly upgraded: you need Workstation 5.x+, VMware Player 1.x+, or VMware Server 1.x+ to power them on after the configure operation.

Converter does not distinguish between physical serial ports and virtual serial ports on the source machine
Virtual serial ports are treated as physical serial ports during the migration. For instance, if a source machine has two physical serial ports and two virtual serial ports, the import creates four serial ports on the destination machine.

Converter fails with a runtime error
If your user name contains the characters ! or &, Converter can fail with the message, ERROR Runtime error, this application has requested the runtime to terminate it in an unusual way. Please contact application support team.

Converter does not uninstall the Converter Agent from a Windows 2000 remote physical machine
While uninstalling the Converter Agent from a Windows 2000 remote physical machine, the task can fail at 99 percent. Attempting to manually uninstall the Agent can fail as well. Workaround: Reboot the remote source machine and uninstall VMware Converter Agent manually using "Add or Remove Programs" in the Control Panel.

Converter Agent might not run after installation and reboot on Windows 2000 and Windows NT4
On certain slow machines, you might get an error stating the Converter Agent is not running when you attempt to launch it. Windows Service Control Manager has timed out after 30 seconds. Workaround: Set the ServicePipeTimeout value under HKEY_LOCAL_ MACHINE\SYSTEM\CurrentControlset\Control to 120000 (120 seconds).

Importing a Windows 2000 virtual machine fails when an OEM-type partition is selected
When selecting individual volumes for a clone, with or without resizing the volumes, do not select any OEM or diagnostic partitions on the disk. The only volumes needed are the active, system, and any data partitions.


MANAGED PRODUCTS

Remote hot clone to a managed destination fails if the source virtual machine is not able to reach the destination without the fully qualified hostname
When doing a remote hot clone to ESX Server, you might see the following error in the Datastore selection page if you do not provide the Fully Qualified name and if the source machine cannot resolve non-Fully Qualified names: Unable to find the server. Please verify that the server name is correct and then try again.
Workaround: Use Fully Qualified names.

Cloning a large disk with lots of free space to an ESX Server destination fails
Selecting "Import all disks and maintain size" on the Converter wizard Source Data page when converting a large disk with lots of free space to an ESX Server destination can cause the import to fail. Check the logs, and if there are error messages with NFC failures, use the "Import volumes . . ." method with or without resizing.

Converter does not support, as destinations, clusters in which the VMware DRS is set to partially automated or fully automated.
For a destination, choosing a cluster with an automated DRS setting produces an error message: "Sorry, automated clusters not yet supported." Converter can import to a cluster only if its DRS settings are set to manual instead of automatic.


THIRD-PARTY FORMATS

Converter does not prevent incompatible imports of certain third-party images
In Converter, you can import third-party images with guest operating systems that are the same version or lower than that of the host operating system. However, Converter does not prevent you from doing an incompatible import, and the resulting task fails. Workaround: Make sure that the guest and host operating systems are compatible before creating a task.

Separate backups should be stored in different folders
Storing more than one third-party backup in a single folder results in a failed migration. Before using Converter to import the image, each backup should be placed in its own folder.

Target virtual machine might not boot up because an incorrect disk number is reported from Symantec backups
In some circumstances, the disk number reported in the Symantec library is incorrect, which causes the resulting image to be unbootable because the virtual machine searches for the Master Boot Record (MBR) in the incorrect device. Workaround: In the main Workstation menu, choose VM > Settings > Hard Disk > Advanced and switch the virtual device node so the target virtual machine boots from the same disk as the source machine.

Resolved Issues

The following are known issues in Converter that have since been resolved.


GENERAL

  • New Hot clone of Windows operating system fails with Platform Error fault 23. Release 3.0.3 corrects this problem.
  • New Importing Acronis images with foreign characters in the path or filename causes error. Release 3.0.3 corrects this problem.
  • New If you attempt to hot clone a Windows physical machine and the source machine uses Windows software mirroring, the import fails with an error message. Release 3.0.3 Fixes this problem.
  • New Importing a virtual machine with a Linux guest operating system to an ESX destination fails during virtual machine creation. Release 3.0.3 fixes this problem. You can now import a machine whose guest operating system is not supported by an ESX destination machine. However, you cannot import a 64-bit guest operating system to a ESX 2.5 destination.
  • New Converter does not import Windows NT 4 with mirrored/striped volumes. Release 3.0.3 fixes this problem. Converter can now import Windows NT4 with mirror volumes for cold and hot cloning and virtual machine images.
  • Tools installation fails on Windows NT4 systems. Release 3.0.2 Update 1 corrects this problem.
  • Customization fails when both Customization and Tools Install are selected because the tools installation process causes the target virtual machine to reboot, which stops the customization process. Release 3.0.2 Update 1 corrects this problem.
  • Restoring a virtual machine with independent disks fails because Converter tries to restore the disks from the backup image, even though VMware Infrastructure Consolidated Backup does not backup independent disks. Release 3.0.2 Update1 corrects this problem.
  • Incorrect message about hardware compatibility during linked clone. Release 3.0.2 corrects this problem.
  • Hot cloning fails with a source machine that is low on disk space. Release 3.0.2 corrects this problem.
  • Virtual machines imported from .sv2i images of systems with diagnostic partitions might not boot because the imported image is not complete and the diagnostic partition is missing. Release 3.0.2 corrects this problem.
  • Converter cannot hot clone a remote physical machine that has Workstation 6 installed. Release 3.0.2 corrects this problem.
  • Import of a Windows 2003 machine to a managed destination fails with an unhelpful help message when a virtual machine with the same name already exists on the destination. Release 3.0.2 corrects this problem.
  • Remote hot clone of the same source machine can fail the second time. Release 3.0.2 corrects this problem.
  • Converter 3.0 could fail in a hot clone of a physical machine configured with dynamic disks. Release 3.0.1 corrects this problem.
  • Converter 3.0 permitted users to mount a read-only network share as the %TEMP% directory during cold cloning, which would result in an error. Release 3.0.1 corrects this problem.
  • Cloning of some hosts, especially if they had diagnostic partitions, could fail during post-processing with "can't create undo folder" error messages at the end of the log. This release fixes the problem by correcting the handling of boot.ini.
  • Converter decreased RAM by 4MB in the destination virtual machine. This problem is fixed in this release.
  • Converter could fail if you selected 0 NICs in the destination virtual machine and also selected any Customization options. Release 3.0.1 corrects this problem.

HOSTED PRODUCTS

  • Installing Converter on a system with Workstation 6 beta installed could lead to unexpected errors. Workstation 6 beta 3 fixed coexistence issues between it and Converter 3.