Provided by: libguestfs-tools_1.40.2-2ubuntu6_amd64 bug


       virt-v2v-input-xen - Using virt-v2v to convert guests from Xen


        export LIBGUESTFS_BACKEND=direct
        virt-v2v -ic 'xen+ssh://' GUEST_NAME [-o* options]


       This page documents how to use virt-v2v(1) to convert guests from RHEL 5 Xen, or SLES and
       OpenSUSE Xen hosts.


   Set up ssh-agent access to Xen host
       Currently you must enable passwordless SSH access to the remote Xen host from the virt-v2v
       conversion server.

       You must also use ssh-agent, and add your ssh public key to /root/.ssh/authorized_keys (on
       the Xen host).

       After doing this, you should check that passwordless access works from the virt-v2v server
       to the Xen host.  For example:

        $ ssh
        [ logs straight into the shell, no password is requested ]

       Note that password-interactive and Kerberos access are not supported.  You have to set up
       ssh access using ssh-agent and authorized_keys.

       With some modern ssh implementations, legacy crypto policies required to interoperate with
       RHEL 5 sshd are disabled.  To enable them you may need to run this command on the
       conversion server (ie. ssh client), but read update-crypto-policies(8) first:

        # update-crypto-policies LEGACY

   Test libvirt connection to remote Xen host
       Use the virsh(1) command to list the guests on the remote Xen host:

        $ virsh -c xen+ssh:// list --all
         Id    Name                           State
         0     Domain-0                       running
         -     rhel49-x86_64-pv               shut off

       You should also try dumping the metadata from any guest on your server, like this:

        $ virsh -c xen+ssh:// dumpxml rhel49-x86_64-pv
        <domain type='xen'>

       If the above commands do not work, then virt-v2v is not going to work either.  Fix your
       libvirt configuration or the remote server before continuing.

       If the guest disks are located on a host block device, then the conversion will fail.  See
       "Xen or ssh conversions from block devices" below for a workaround.

   Importing a guest
       To import a particular guest from a Xen server, do:

        $ LIBGUESTFS_BACKEND=direct \
              virt-v2v -ic 'xen+ssh://' \
                  rhel49-x86_64-pv \
                  -o local -os /var/tmp

       where "rhel49-x86_64-pv" is the name of the guest (which must be shut down).

       In this case the output flags are set to write the converted guest to a temporary
       directory as this is just an example, but you can also write to libvirt or any other
       supported target.

       Setting the backend to "direct" is a temporary workaround until libvirt bug 1140166 is

   Xen or ssh conversions from block devices
       Currently virt-v2v cannot directly access a Xen guest (or any guest located remotely over
       ssh) if that guest’s disks are located on host block devices.

       To tell if a Xen guest uses host block devices, look at the guest XML.  You will see:

         <disk type='block' device='disk'>
           <source dev='/dev/VG/guest'/>

       where "type='block'", "source dev=" and "/dev/..." are all indications that the disk is
       located on a host block device.

       This happens because the qemu ssh block driver that we use to access remote disks uses the
       ssh sftp protocol, and this protocol cannot correctly detect the size of host block

       The workaround is to copy the guest over to the conversion server, using the separate
       virt-v2v-copy-to-local(1) tool, followed by running virt-v2v.  You will need sufficient
       space on the conversion server to store a full copy of the guest.

        virt-v2v-copy-to-local -ic xen+ssh:// guest
        virt-v2v -i libvirtxml guest.xml -o local -os /var/tmp
        rm guest.xml guest-disk*




       Richard W.M. Jones


       Copyright (C) 2009-2019 Red Hat Inc.



       To get a list of bugs against libguestfs, use this link:

       To report a new bug against libguestfs, use this link:

       When reporting a bug, please supply:

       ·   The version of libguestfs.

       ·   Where you got libguestfs (eg. which Linux distro, compiled from source, etc)

       ·   Describe the bug accurately and give a way to reproduce it.

       ·   Run libguestfs-test-tool(1) and paste the complete, unedited output into the bug