Reference Guide

vConverter v4.1 Chapter 1 Introduction 7
4BConversion Process Overview
The vConverter architecture includes the GUI, the Source Quiesce, Drive Capture Tool
(DCT), Migration Tool, and ESX/Xen Host Daemon. The Source Quiesce, Capture Tool,
and Migration Tool are all directed from the GUI onto the source by the Interactive
Remote Launch Tool (IRLT). Conversion jobs are configured, scheduled, and initiated by
the GUI component. During conversions, job details are sent to the source, which is
paused. Data is sent from the source to the target ESX/Xen host. Status messages are
returned from the Source Server Capture Driver (SSCD) to update the information in the
GUI. Upon completion of the data transfer, the ESX/Xen Host Daemon can resize the
partitions and perform the P2V conversion steps. The VM is configured with the proper
CPU, memory, and network settings, and registered on the ESX host. Then, it is ready to
be run as a VM.
Note: For Windows XP and Windows Server 2003, the Microsoft Volume Shadow Copy
Service (MS VSS) is used instead of Consistency Driver to enforce consistency for
applications.
What Is Happening on the ESX Host?
At the ESX host level, the process is extremely fast and flexible with minimal impact to
the virtual environment. These application components are used:
• xinetd—The built-in service console method for listening to new traffic and
starting server components when required by an external request.
• vzBoost—A controllable VMkernel module that allows data to be written at very
fast speeds directly through the service console. vzBoost is an optional installation
component.
• sftp-over-tcp—The server component that makes data transfer possible. It is based
on the SFTP, with the secure elements eliminated to make it as fast and