virt-v2v
converts virtual machines from a foreign hypervisor to run on Red Hat Enterprise Virtualization. It automatically packages the virtual machine images and metadata, then uploads them to a Red Hat Enterprise Virtualization export storage domain. For more information on export storage domains, see Section 3.2, “Attaching an Export Storage Domain”. virt-v2v
always makes a copy of storage before conversion.
virt-v2v
can transfer the converted VM directly to an NFS export storage domain. From the export storage domain, the VM can be imported into a Red Hat Enterprise Virtualization Data Center. The storage domain must be mountable by the machine running virt-v2v
. When exporting to a Red Hat Enterprise Virtualization export domain, virt-v2v
must run as root.
rpcbind
and nfslock
services must be running on the host used to run virt-v2v
. The network must also be configured to allow NFS access to the storage server. For more details refer to the Red Hat Enterprise Linux Storage Administration Guide.
virt-v2v.conf
. This step is optional, and is not required for most use cases.
/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 you are converting a virtual machine for output to both libvirt and Red Hat Enterprise Virtualization, separate virt-v2v.conf
files should be used for each conversion. This is because the destination network bridge corresponding to the same source network bridge is usually different for libvirt and Red Hat Enterprise Virtualization output.
--network
or --bridge
parameters, rather than modifying virt-v2v.conf
.
virt-v2v.conf
. This step is optional. Profiles specify a conversion method, storage location, output format and allocation policy. When a profile is defined, it can be called using --profile
rather than individually providing the -o
, -os
, -of
and -oa
parameters. See virt-v2v.conf(5) for details.
virt-v2v
may install a new kernel and drivers on the virtual machine. If the virtual machine being converted is registered to Red Hat Network (RHN), the required packages will be automatically downloaded. If the virtual machine is not registered to RHN, the virt-v2v.db
file ships with a list of RPMs used for this purpose. The RPMs relevant to your virtual machine must be downloaded manually from RHN and made available on the host running virt-v2v
. The RPMs should be saved in the directory specified by the path-root
configuration element, which by default is /var/lib/virt-v2v/software/
. virt-v2v
will display an error similar to Example 2.1, “Missing Package error” if software it depends upon for a particular conversion is not available.
virt-v2v: Installation failed because the following files referenced in the configuration file are required, but missing: rhel/6/kernel-2.6.32-128.el6.x86_64.rpm rhel/6/ecryptfs-utils-82-6.el6.x86_64.rpm rhel/6/ecryptfs-utils-82-6.el6.i686.rpm
/var/lib/virt-v2v/software
. For Red Hat Enterprise Linux 6, the directory is /var/lib/virt-v2v/software/rhel/6
virt-v2v
. This package provides support for NTFS, which is used by many Windows systems. The libguestfs-winsupport package is provided by the RHEL V2VWIN (v. 6 for 64-bit x86_64) channel. Ensure your system is subscribed to this channel, then run the following command as root:
yum install libguestfs-winsupport
No operating system could be detected inside this disk image. This may be because the file is not a disk image, or is not a virtual machine image, or because the OS type is not understood by virt-inspector. If you feel this is an error, please file a bug report including as much information about the disk image as possible.
virt-v2v
. This package provides para-virtualized block and network drivers for Windows guests. The virtio-win package is provided by the RHEL Server Supplementary (v. 6 64-bit x86_64) channel. Ensure your system is subscribed to this channel, then run the following command as root:
yum install virtio-win
virt-v2v: Installation failed because the following files referenced in the configuration file are required, but missing: /usr/share/virtio-win/drivers/i386/Win2008
virsh dumpxml vm-name > vm-name.xmlThis will require booting into a Xen kernel to obtain the XML, as libvirt needs to connect to a running Xen hypervisor to obtain its metadata. The conversion process is optimized for KVM, so obtaining domain data while running a Xen kernel, then performing the conversion using a KVM kernel will be more efficient than running the conversion on a Xen kernel.