virt-v2v-input-xen(1)

1virt-v2v-input-xen(1)       Virtualization Support       virt-v2v-input-xen(1)
2
3
4

NAME

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

SYNOPSIS

9        virt-v2v -ic 'xen+ssh://root@xen.example.com'
10                 -ip passwordfile
11                 GUEST_NAME [-o* options]
12

DESCRIPTION

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

INPUT FROM XEN

18   SSH authentication
19       You can use SSH password authentication, by supplying the name of a
20       file containing the password to the -ip option (note this option does
21       not take the password directly).  You may need to adjust
22       /etc/ssh/sshd_config on the Xen server to set "PasswordAuthentication
23       yes".
24
25       If you are not using password authentication, an alternative is to use
26       ssh-agent, and add your ssh public key to /root/.ssh/authorized_keys
27       (on the Xen host).  After doing this, you should check that
28       passwordless access works from the virt-v2v server to the Xen host.
29       For example:
30
31        $ ssh root@xen.example.com
32        [ logs straight into the shell, no password is requested ]
33
34       With some modern ssh implementations, legacy crypto policies required
35       to interoperate with RHEL 5 sshd are disabled.  To enable them you may
36       need to run this command on the conversion server (ie. ssh client), but
37       read update-crypto-policies(8) first:
38
39        # update-crypto-policies --set LEGACY
40
41   Test libvirt connection to remote Xen host
42       Use the virsh(1) command to list the guests on the remote Xen host:
43
44        $ virsh -c xen+ssh://root@xen.example.com list --all
45         Id    Name                           State
46        ----------------------------------------------------
47         0     Domain-0                       running
48         -     rhel49-x86_64-pv               shut off
49
50       You should also try dumping the metadata from any guest on your server,
51       like this:
52
53        $ virsh -c xen+ssh://root@xen.example.com dumpxml rhel49-x86_64-pv
54        <domain type='xen'>
55          <name>rhel49-x86_64-pv</name>
56          [...]
57        </domain>
58
59       If the above commands do not work, then virt-v2v is not going to work
60       either.  Fix your libvirt configuration or the remote server before
61       continuing.
62
63       If the guest disks are located on a host block device, then the
64       conversion will fail.  See "Xen or ssh conversions from block devices"
65       below for a workaround.
66
67   Importing a guest
68       To import a particular guest from a Xen server, do:
69
70        $ virt-v2v -ic 'xen+ssh://root@xen.example.com' \
71                  rhel49-x86_64-pv \
72                  -o local -os /var/tmp
73
74       where "rhel49-x86_64-pv" is the name of the guest (which must be shut
75       down).
76
77       In this case the output flags are set to write the converted guest to a
78       temporary directory as this is just an example, but you can also write
79       to libvirt or any other supported target.
80
81   Xen or ssh conversions from block devices
82       Currently virt-v2v cannot directly access a Xen guest (or any guest
83       located remotely over ssh) if that guest’s disks are located on host
84       block devices.
85
86       To tell if a Xen guest uses host block devices, look at the guest XML.
87       You will see:
88
89         <disk type='block' device='disk'>
90           ...
91           <source dev='/dev/VG/guest'/>
92
93       where "type='block'", "source dev=" and "/dev/..." are all indications
94       that the disk is located on a host block device.
95
96       This happens because the qemu ssh block driver that we use to access
97       remote disks uses the ssh sftp protocol, and this protocol cannot
98       correctly detect the size of host block devices.
99
100       The workaround is to copy the block device from the remote Xen server
101       to a regular local file, copy the libvirt guest XML, adjust the "disk"
102       element to point to the local file, and use "-i libvirtxml" mode
103       instead.
104

AUTHOR

109       Richard W.M. Jones
110

COPYRIGHT

112       Copyright (C) 2009-2020 Red Hat Inc.
113

LICENSE

115       This program is free software; you can redistribute it and/or modify it
116       under the terms of the GNU General Public License as published by the
117       Free Software Foundation; either version 2 of the License, or (at your
118       option) any later version.
119
120       This program is distributed in the hope that it will be useful, but
121       WITHOUT ANY WARRANTY; without even the implied warranty of
122       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
123       General Public License for more details.
124
125       You should have received a copy of the GNU General Public License along
126       with this program; if not, write to the Free Software Foundation, Inc.,
127       51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
128

BUGS

130       To get a list of bugs against libguestfs, use this link:
131       https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
132
133       To report a new bug against libguestfs, use this link:
134       https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
135
136       When reporting a bug, please supply:
137
138       •   The version of libguestfs.
139
140       •   Where you got libguestfs (eg. which Linux distro, compiled from
141           source, etc)
142
143       •   Describe the bug accurately and give a way to reproduce it.
144
145       •   Run libguestfs-test-tool(1) and paste the complete, unedited output
146           into the bug report.
147
148
149
150virt-v2v-2.0.7                    2022-07-06             virt-v2v-input-xen(1)