5.5
Table Of Contents
- VMware vCenter Converter Standalone User's Guide
- Contents
- About This Book
- Introduction to VMware vCenter Converter Standalone
- Migration with Converter Standalone
- Converter Standalone Components
- Cloning and System Configuration of Physical Machines
- Types of Data Cloning Operations
- Using Converter Standalone with Virtual Machine Sources and System Images
- System Settings Affected by Conversion
- Changes to Virtual Hardware After Virtual Machine Migration
- System Requirements
- Supported Operating Systems
- Supported Firmware Interfaces
- Supported Source Types
- Supported Destination Types
- Supported Source Disk Types
- Supported Destination Disk Types
- Support for IPv6 in Converter Standalone
- Installation Space Requirements
- Screen Resolution Requirements
- Configuring Permissions for vCenter Users
- TCP/IP and UDP Port Requirements for Conversion
- Requirements for Remote Hot Cloning of Windows Operating Systems
- Conversion Limitations
- Installing and Uninstalling Converter Standalone
- Perform a Local Installation on Windows
- Perform a Client-Server Installation in Windows
- Perform a Command-Line Installation in Windows
- Command-Line Options for Windows Installation
- Modify Converter Standalone in Windows
- Repair Converter Standalone in Windows
- Uninstall Converter Standalone in Windows
- Connect to a Remote Converter Standalone Server
- Convert a Physical or Virtual Machine
- Start the Wizard for a Conversion
- Select a Source Machine to Convert
- Select a Powered On Windows Machine to Convert
- Select a Powered On Linux Machine to Convert
- Select an ESX/ ESXi or vCenter Server Virtual Machine to Convert
- Select a VMware Hosted Virtual Machine to Convert
- Select a Backup Image or a Third-Party Virtual Machine to Convert
- Select a Hyper-V Server Virtual Machine to Convert
- Select a Destination for the New Virtual Machine
- Configure the Hardware of the Destination Virtual Machine
- Organize the Data to Be Copied on the Destination Machine
- Resize a Volume
- Change a Volume Cluster Size
- Exclude a Source Volume from the Conversion Process
- Move a Volume to a Different Virtual Disk
- Select the Destination Datastore for a Source Volume
- Add a Virtual Disk
- Set Up a Virtual Disk as a Logical-Volume Group Container
- Move a Disk to a Different Datastore
- Create an Expandable Disk on a Managed Destination
- Create an Expandable Disk on a Hosted Destination
- Exclude a Source Disk from the Conversion Process
- Copy All Disks to the Destination
- Create an Optimized Partition Layout
- Create a Linked Clone
- Edit the Number of Processor Sockets and Cores
- Allocate Memory for the Destination Virtual Machine
- Select a Disk Controller for the Destination Virtual Machine
- Configure the Network Settings of the Destination Virtual Machine
- Configure the Network for the Helper Virtual Machine
- Organize the Data to Be Copied on the Destination Machine
- Configure the Software on the Destination Virtual Machine
- Configure the Conversion Job
- Set the Startup Mode for Destination Services
- Stop Services Running on the Source Machine
- Synchronize the Destination Machine with Changes Made to the Source Machine
- Power Off the Source Machine After Conversion
- Power On the Destination Virtual Machine After Conversion
- Limit the Amount of Resources Used by the Conversion Job
- Uninstall Converter Standalone Agent from the Source Machine
- Review the Summary and Submit the Conversion Job
- Configure Virtual Machines
- Save Sysprep Files
- Start the Configuration Wizard
- Select a Source Machine to Configure
- Select the Options to Configure
- Review and Submit the Configuration Job
- Manage Conversion and Configuration Jobs and Tasks
- Index
Conversion Limitations 3
When you are aware of the conversion limitations of Converter Standalone, you might be able to avoid
conversion and post-conversion problems, and handle them more easily.
This chapter includes the following topics:
n
“Conversion Limitations for Powered On Machines,” on page 29
n
“Conversion Limitations for VMware Virtual Machines,” on page 29
n
“Conversion Limitations for Third-Party Virtual Machines or System Images,” on page 30
n
“Limitations Related to Creating Snapshots of Windows Sources,” on page 31
Conversion Limitations for Powered On Machines
When you convert a powered on machine, some conversion features might not be available for certain
source operating systems.
Table 3‑1. Limitations for Powered On Machine Conversion
Source Operating System Limitations
Windows XP and later
n
When you convert UEFI sources, Converter Standalone does not copy any UEFI
variables to the destination.
n
Synchronization is supported only for volume-based cloning at the block level.
Linux
n
Only volume-based cloning at the file level is supported.
n
Only managed destinations are supported.
n
Converting multiboot virtual machines is supported only if GRUB is installed as the
boot loader. LILO is not supported.
n
When you convert UEFI sources, Converter Standalone copies only the current
UEFI boot entry option to the destination.
n
Simultaneous cloning of multiple disks and volumes is supported only when
converting a virtual Linux source.
n
Converting machines with boot directory located on a LVM logical volume is not
supported. The boot directory must be located on a basic volume.
n
Installing VMware Tools on Linux guest operating systems is not supported.
Conversion Limitations for VMware Virtual Machines
Certain limitations exist when you convert a VMware virtual machine.
You must power off source virtual machines before you convert them. You can convert running virtual
machines if you follow the procedure for converting powered on machines.
VMware, Inc.
29