23.2.2. Converting a local Xen virtualized guest
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 -op pool --bridge brname vm-name.xml
pool is the local storage pool to hold the image,
brname is the name of a local network bridge to connect the converted guest's network to, and
vm-name.xml is the path to the virtualized guest's exported XML. You may also use the
--network parameter to connect to a locally managed network, or specify multiple mappings in
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.