1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
=head1 NAME
virt-v2v-copy-to-local - Copy a remote guest to the local machine
=head1 SYNOPSIS
virt-v2v-copy-to-local -ic LIBVIRT_URI GUEST
virt-v2v-copy-to-local -ic xen+ssh://root@xen.example.com xen_guest
=head1 DESCRIPTION
C<virt-v2v-copy-to-local> copies a guest from a remote hypervisor to
the local machine, in preparation for conversion by L<virt-v2v(1)>.
Note this tool alone B<does not> do the virt-v2v conversion.
=head2 When to use this tool
This tool is not usually necessary, but there are a few special cases
(see list below) where you might need it.
If your case does not fit one of these special cases, then ignore this
tool and read L<virt-v2v(1)> instead. The virt-v2v-copy-to-local
process is slower than using virt-v2v directly, because it has to copy
unused parts of the guest disk.
=over 4
=item *
You have a Xen guest using host block devices. Virt-v2v cannot
convert such guests directly.
See L<virt-v2v-input-xen(1)>.
=back
=head2 How this tool works
This tool uses libvirt to get the libvirt XML (metadata) of the remote
guest, essentially equivalent to running C<virsh dumpxml guest>.
It then uses the XML to locate the remote guest disks, which are
copied over using a hypervisor-specific method. It uses ssh for
remote Xen hypervisors.
It then modifies the libvirt XML so that it points at the local copies
of the guest disks.
The libvirt XML is output to a file called F<guest.xml> (where
I<guest> is the name of the guest). The disk(s) are output to file(s)
called F<guest-disk1>, F<guest-disk2> and so on.
After copying the guest locally, you can convert it using:
virt-v2v -i libvirtxml guest.xml [-o options ...]
Virt-v2v finds the local copies of the disks by looking in the XML.
=head1 EXAMPLES
=head2 Copy and convert from Xen hypervisor that uses host block devices
For full instructions, see L<virt-v2v-input-xen(1)>.
virt-v2v-copy-to-local -ic xen+ssh://root@xen.example.com xen_guest
virt-v2v -i libvirtxml xen_guest.xml -o local -os /var/tmp
rm xen_guest.xml xen_guest-disk*
=head1 OPTIONS
=over 4
=item B<--help>
Display help.
=item B<-ic> libvirtURI
Specify a libvirt connection URI
=item B<-ip> file
Instead of asking for password(s) interactively, pass the password
through a file. Note the file should contain the whole password,
B<without any trailing newline>, and for security the file should have
mode C<0600> so that others cannot read it.
Currently this option does not have any effect on xen+ssh transfers,
but that is a bug.
=item B<-q>
=item B<--quiet>
This disables progress bars and other unnecessary output.
=item B<-v>
=item B<--verbose>
Enable verbose messages for debugging.
=item B<-V>
=item B<--version>
Display version number and exit.
=back
=head1 SEE ALSO
L<virt-v2v(1)>,
L<virsh(1)>,
L<http://libguestfs.org/>,
L<https://libvirt.org/uri.html>,
L<https://libvirt.org/remote.html>.
=head1 AUTHORS
Richard W.M. Jones L<http://people.redhat.com/~rjones/>
=head1 COPYRIGHT
Copyright (C) 2009-2019 Red Hat Inc.
|
