Installation guide

Preparing to convert a virtualized guest
173
Figure 23.3. Adding a storage pool
2. Create local network interfaces.
The local machine must have an appropriate network to which the converted virtualized guest can
connect. This is likely to be a bridge interface. A bridge interface can be created using standard
tools on the host. Since version 0.8.3, virt-manager can also create and manage bridges.
3. Specify network mappings in virt-v2v.conf. This step is optional, and is not required for most
use cases.
If your virtualized guest has multiple network interfaces, /etc/virt-v2v.conf must be edited
to specify the network mapping for all interfaces. You can specify an alternative virt-v2v.conf
file with the -f parameter.
If your virtualized guest only has a single network interface, it is simpler to use the --network or
--bridge parameters, rather than modifying virt-v2v.conf.
Preparing to convert a virtualized guest running Linux
Before a virtualized guest running Linux can be converted, ensure that the following steps are
completed.
1. Obtain the software
As part of the conversion process, virt-v2v may install a new kernel and drivers on the
virtualized guest. If the host running virt-v2v is registered to Red Hat Network (RHN), the
required packages will be automatically downloaded. For environments where RHN is not
available, the virt-v2v.conf file references a list of RPMs used for this purpose. The RPMs
relevant to your virtualized guest must be downloaded manually from RHN and made available
in the directory specified by the path-root configuration element, which by default is /var/lib/