Installation guide

Chapter 23. Migrating to KVM from other hypervisors using virt-v2v
178
Authenticating to the ESX server
Connecting to the ESX server will require authentication. virt-v2v supports password authentication
when connecting to ESX. It reads passwords from $HOME/.netrc. The format of this file is described in
the netrc(5) man page. An example entry is:
machine esx.example.com login root password s3cr3t
.netrc permissions
The .netrc file must have a permission mask of 0600 to be read correctly by virt-v2v
Connecting to an ESX server with an invalid certificate
In non-production environments, the ESX server may have a non-valid certificate, for example a self-
signed certificate. In this case, certificate checking can be explicitly disabled by adding '?no_verify=1'
to the connection URI as shown below:
... -ic esx://esx.example.com/?no_verify=1 ...
23.2.5. Converting a virtualized guest running Windows
Important
Virtualized guests running Windows can only be converted for output to Red Hat Enterprise
Virtualization. The conversion procedure depends on post-processing by the Red Hat Enterprise
Virtualization Manager for completion. See Section 23.4.2, “Configuration changes for Windows
virtualized guests” for details of the process. Virtualized guests running Windows cannot be
converted for output to libvirt.
This example demonstrates converting a local Xen virtualized guest running Windows for output to
Red Hat Enterprise Virtualization. Ensure that the virtualized guest's XML is available locally, and that
the storage referred to in the XML is available locally at the same paths.
To convert the virtualized guest from an XML file, run:
virt-v2v -i libvirtxml -o rhev -osd storage.example.com:/exportdomain --network rhevm vm-
name.xml
Where vm-name.xml is the path to the virtualized guest's exported xml, and
storage.example.com:/exportdomain is the export storage domain. You may also use the --
network parameter to connect to a locally managed network, or specify multiple mappings in /etc/
virt-v2v.conf.
If your guest uses a Xen para-virtualized kernel (it would be called something like kernel-xen or
kernel-xenU), virt-v2v will attempt to install a new kernel during the conversion process. You can
avoid this requirement by installing a regular kernel, which won't reference a hypervisor in its name,
alongside the Xen kernel prior to conversion. You should not make this newly installed kernel your
default kernel, because Xen will not boot it. virt-v2v will make it the default during conversion.