Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Best practices for using and troubleshooting VMware Converter (1004588)

Last Updated: 11/20/2022Categories: Best PracticesTotal Views: 397623Language:
Chinese (Simplified)Portuguese (European)KoreanJapaneseSpanishEnglish

20 like this article

Subscribe to get an email
newsletter with new updates

20 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

No keyboard or mouse in a converted virtual machine

You see one of these messages in an error dialog:

Unknown error returned by VMware Converter Agent

Out of disk space

You see one of these messages in a VMware Converter log file:

Failed to establish Vim connection

Import host not found

P2VError UFAD_SYSTEM_ERROR(Internal Error)

Pcopy_CloneTree failed with err=80

The file exists (80)

Failed to connect

Giving up trying to connect

Failed to take snapshot of the source volume

stcbasic.sys not installed or snapshot creation failed. err=2

Can't create undo folder

sysimage.fault.FileCreateError

sysimage.fault.ReconfigFault

sysimage.fault.PlatformError

Number of virtual devices exceeds maximum for a given controller

TooManyDevices

QueryDosDevice: ret=270 size=1024 err=0

Error opening disk device: Incorrect function (1)

Vsnap does not have admin rights

Specified key identifier already exists

vim.fault.NoDiskSpac

Purpose

This article describes various best practice techniques that can be followed to minimize potential problems when using the VMware Converter product.

Take note of the procedures outlined in this article. While not all steps may apply to your situation, if one of the steps in the article is different from what you had followed in your environment, attempt another conversion after changing your procedure to follow the recommendation in that step.

Resolution

These steps are not a recommendation against using certain features of VMware Converter in normal use, but are a guide to assist in troubleshooting general failures with Converter.

If you encounter a specific failure, open the Converter log file, identify the failure message near the end of the log file and perform a search in the VMware Knowledge Base for more detailed assistance on the issue.

The best approach to converting a Windows operating system to a virtual machine is to perform a hot migration with VMware Converter installed locally in the operating system. If this is not possible, a remote hot migration is the next best choice.

Download Converter from the VMware Download Center.

Note: Currently, only VMware Converter 4.2 and later support physical to virtual machine conversion for Linux sources. For earlier versions of Converter, the support is experimental and some of the features, such as partition resizing, are not available.

Notes and preparation for conversion

To prepare for conversion:

If the source is a domain controller, special considerations must be made. VMware does not recommend virtualizing an active domain controller with Converter. For more information, see Virtualizing existing domain controllers (1006996).

If the source is Microsoft Exchange, SQL, or other database server, VMware recommends that the application (Microsoft Exchange/SQL) and database services be shut down prior to conversion. This minimizes any chance of corrupted database tables or stale data in the destination virtual machine.

Disable the real-time antivirus scanning during the conversion.

Read the VMware Converter Release Notes. The release notes review important limitations or issues that may affect the conversion process.

Verify that you are using or have downloaded the latest version of VMware Converter.
If you have previously installed or attempted a conversion with an earlier version of VMware Converter, a previous version may still be installed.

Uninstall VMware Converter from the source computer:

Click Start > Control Panel > Add / Remove Programs or Programs and Features depending on the Operating System.

Uninstall any version of VMware Converter, Converter agent, or Converter Enterprise.

Restart the server.

Install the latest version of VMware Converter using the local Administrator account. If you are going to use the remote hot clone feature you may choose a custom installation to only install the Converter Agent.

If the server is running Windows 2000 or Windows NT, you must restart the server or Converter does not start.

Install VMware Converter directly to the source operating system using the local Administrator account. If the source server is running Windows NT or Windows 2000, you must reboot it after installing VMware Converter or Converter does not start.

Note: In some cases, a domain administrator account may be used depending on your environment, local and group policies, and account permissions.

If the NIC on the source machine is compatible with TOE (TCP Offload Engine), you need to disable it by running this command in a command prompt on the source machine:

netsh int tcp set global chimney=disabled

Note: The preceding link was correct as of November 21, 2014. If you find the link is broken, provide feedback and a VMware employee will update the link.

Confirm that the source has 200 MB of free disk space on its system volume. This space is required to operate the disk snapshot features in Converter. For more information, see Investigating operating system disk space (1004007).

Note: It is possible to separate the source partitions in different destination volumes during the conversion.

Run VMware Converter as a local administrator. Using a local administrator account removes any possible permissions issues. If you are performing a remote conversion, be sure to specify the login user as the Administrator account.

Note: In some cases a domain administrator account may be used depending on your environment, local and group policies, and account permissions.

Run the System Configuration Utility(msconfig) on the source server to reduce the number of services and applications running on startup, all software except for All Microsoft Services and VMware Converter Service. For more information, see Using the Windows System Configuration utility (1004010).

If you have static IP addresses assigned, assign the interfaces DHCP addresses prior to conversion, if possible.

If the source is a virtual machine created in Microsoft Virtual PC, remove the Virtual PC Additions, prior to conversion.

If the destination is an ESX host:

Connect to the server using its IP address instead of DNS host name. Using the host name of the ESX host may expose issues with DNS name resolution that can prevent the Converter from connecting.

Confirm that the source server can access the destination ESX host directly using ports 443 and 902, even if using VirtualCenter. For more information, see Verifying and troubleshooting networking connections that may cause VMware Converter to fail (1006607).

Authenticate to the ESX host using the root account.

If the source server contains a hard drive or partition larger than 256GB, ensure that the destination datastore's block size is 2MB, 4MB, or 8MB, and not the default 1MB size. The 1 MB default block size cannot accommodate a file larger than 256 GB. The block size is no longer used on a VMFS 5 datastore connected to an ESXi 5.0 Host.

Confirm that you are providing a unique name for the target virtual machine. Use the Virtual Infrastructure (VI) client to confirm that the name is not already in use.

Optimizing the conversion for best success

To set up conversion for the best success:

If you are encountering failures with Converter, reduce the number of optional items in the Conversion Wizard:

Do not convert diagnostic partitions or unrecognized file systems.

If you are experiencing cloning phase failures, do not choose to resize the partitions.

If there are multiple volumes, attempt converting only the system volume.

If you are experiencing network or Ethernet issues, trying using a different network type. For more information, see Understanding networking types in hosted products (1006480).

Leave the default number of virtual network cards (NICs) unaltered. The number of virtual NICs can be changed after conversion has completed.

Deselect the option to install VMware Tools.

Deselect the option to perform Customization on the virtual machine.

Tasks to perform after conversion has completed

After conversion has completed:

Review the virtual hardware settings:

Adjust the number of virtual NICs. If you need to customize the host name or IP address, leave all NICs disconnected but present.

Remove any unnecessary devices such as USB controllers (if running on ESX), COM ports or floppy drives

Start the virtual machine in Safe Mode. For more information, see Booting a Windows guest operating system into Safe Mode (1004011).

Click Start > Control Panel > Add / Remove Programs. Remove any unnecessary programs used to install or support device drivers, such a RAID management tools, network teaming or management software, wireless card management software, and video and sound drivers. Do not restart if prompted by an uninstall program.

Restart the virtual machine into Normal mode.

Remove any additional devices or device drivers that were used to support hardware on the physical server. Use either the Device Manager or Control Panel, depending on the version of Windows, to remove unnecessary devices. It may also be necessary to view the Event Log to clear any remaining device startup failure messages.

Note: To remove the hidden devices from the Windows operating system, follow the instructions in the Microsoft Knowledge Base article 315539.

Note: The preceding link was correct as of November 21, 2014. If you find the link is broken, provide feedback and a VMware employee will update the link.

VMware recommends changing the HAL in the virtual machine to uniprocessor if the source server is configured with multi-CPU hardware abstraction layer (HAL), and the destination virtual machine is configured to use a single CPU. For more information, see Modifying the Hardware Abstraction Layer (HAL) for a Windows virtual machine (1003978).

Install VMware Tools and restart if prompted.

If required, customize the virtual machine's identity. VMware recommends using the Microsoft Sysprep utility to accomplish this, however it can also be accomplished by manually changing its computer host name, IP address, and any other required unique identification. For more information, see Microsoft's article How to Use Sysprep: An Introduction.

Note: The preceding link was correct as of November 21, 2014. If you find the link is broken, provide feedback and a VMware employee will update the link.

If the System Configuration Utility(msconfig) was used prior to conversion, select the Normal startup option to change switch back to a normal boot configuration. For more information, see Using the Windows System Configuration utility (1004010).

Apply any previously removed static IP address settings, as required.

Reconnect any disconnected virtual NICs, as required.

Related Information

VMware Skyline Health Diagnostics for vSphere - FAQ

For additional administration and management information about VMware converter 6.0, see VMware vCenter Converter Standalone User's Guide for vCenter Converter Standalone 6.3

For additional detail and information on troubleshooting issues with VMware Converter, see Troubleshooting checklist for VMware Converter (1016330).

For further troubleshooting information, you can enable verbose logging in vCenter Converter. For more information, see Increasing the logging levels to verbose for vCenter Converter application components (2008019).

For the list of supported guest operating systems, see the VMware vCenter Converter Standalone Release Notes .

Note: Please go through the release notes of VMware vCenter Converter Standalone 6.3 to check what versions of guest operating is not supported.

Modifying the Hardware Abstraction Layer (HAL) for a Windows virtual machine
Investigating operating system disk space
Using the Windows System Configuration utility
Booting a Windows guest operating system into Safe Mode
Understanding networking types in hosted products
Verifying and troubleshooting networking connections that may cause VMware Converter to fail
Virtualizing existing domain controllers in VMware vCenter Converter
Collecting diagnostic information for VMware Converter
Troubleshooting checklist for VMware Converter
Recomendaciones sobre el uso y la solución de problemas de VMware Converter
VMware Converter の使用およびトラブルシューティングのベスト プラクティス
Converting a physical or virtual machine with VMware Converter takes longer than expected
Increasing the logging levels to verbose for vCenter Converter application components
Práticas recomendadas para uso e diagnóstico de VMware Converter
Prácticas recomendadas para el uso y la resolución de problemas de VMware Converter
VMware Converter 的使用与故障排除最佳做法

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)KoreanJapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Converter Standalone

VMware vCenter Converter

Related Versions:

VMware vCenter Converter Standalone 6.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant