1virt-v2v-output-rhv(1)      Virtualization Support      virt-v2v-output-rhv(1)
2
3
4

NAME

6       virt-v2v-output-rhv - Using virt-v2v to convert guests to oVirt or RHV
7

SYNOPSIS

9        virt-v2v [-i* options] -o rhv-upload [-oc ENGINE_URL] -os STORAGE
10                               [-op PASSWORD] [-of raw]
11                               [-oo rhv-cafile=FILE]
12                               [-oo rhv-cluster=CLUSTER]
13                               [-oo rhv-direct]
14                               [-oo rhv-verifypeer]
15
16        virt-v2v [-i* options] -o rhv -os [esd:/path|/path]
17
18        virt-v2v [-i* options] -o vdsm
19                               [-oo vdsm-image-uuid=UUID]
20                               [-oo vdsm-vol-uuid=UUID]
21                               [-oo vdsm-vm-uuid=UUID]
22                               [-oo vdsm-ovf-output=DIR]
23

DESCRIPTION

25       This page documents how to use virt-v2v(1) to convert guests to an
26       oVirt or RHV management instance.  There are three output modes that
27       you can select, but only -o rhv-upload should be used normally, the
28       other two are deprecated:
29
30       -o rhv-upload -os STORAGE
31           Full description: "OUTPUT TO RHV"
32
33           This is the modern method for uploading to oVirt/RHV via the REST
34           API.  It requires oVirt/RHV ≥ 4.2.
35
36       -o rhv -os esd:/path
37       -o rhv -os /path
38           Full description: "OUTPUT TO EXPORT STORAGE DOMAIN"
39
40           This is the old method for uploading to oVirt/RHV via the Export
41           Storage Domain (ESD).  The ESD can either be accessed over NFS
42           (using the -os esd:/path form) or if you have already NFS-mounted
43           it somewhere specify the path to the mountpoint as -os /path.
44
45           The Export Storage Domain was deprecated in oVirt 4, and so we
46           expect that this method will stop working at some point in the
47           future.
48
49       -o vdsm
50           This is the old method used internally by the RHV-M user interface.
51           It is never intended to be used directly by end users.
52

OUTPUT TO RHV

54       This new method to upload guests to oVirt or RHV directly via the REST
55       API requires oVirt/RHV ≥ 4.2.
56
57       You need to specify -o rhv-upload as well as the following extra
58       parameters:
59
60       -oc "https://ovirt-engine.example.com/ovirt-engine/api"
61           The URL of the REST API which is usually the server name with
62           "/ovirt-engine/api" appended, but might be different if you
63           installed oVirt Engine on a different path.
64
65           You can optionally add a username and port number to the URL.  If
66           the username is not specified then virt-v2v defaults to using
67           "admin@internal" which is the typical superuser account for oVirt
68           instances.
69
70       -of raw
71           Currently you must use -of raw and you cannot use -oa preallocated.
72
73           These restrictions will be loosened in a future version.
74
75       -op password-file
76           A file containing a password to be used when connecting to the
77           oVirt engine.  Note the file should contain the whole password,
78           without any trailing newline, and for security the file should have
79           mode 0600 so that others cannot read it.
80
81       -os "ovirt-data"
82           The storage domain.
83
84       -oo rhv-cafile=ca.pem
85           The ca.pem file (Certificate Authority), copied from
86           /etc/pki/ovirt-engine/ca.pem on the oVirt engine.
87
88       -oo rhv-cluster="CLUSTERNAME"
89           Set the RHV Cluster Name.  If not given it uses "Default".
90
91       -oo rhv-direct
92           If this option is given then virt-v2v will attempt to directly
93           upload the disk to the oVirt node, otherwise it will proxy the
94           upload through the oVirt engine.  Direct upload requires that you
95           have network access to the oVirt nodes.  Non-direct upload is
96           slightly slower but should work in all situations.
97
98       -oo rhv-verifypeer
99           Verify the oVirt/RHV server’s identity by checking the server‘s
100           certificate against the Certificate Authority.
101

OUTPUT TO EXPORT STORAGE DOMAIN

103       This section only applies to the -o rhv output mode.  If you use
104       virt-v2v from the RHV-M user interface, then behind the scenes the
105       import is managed by VDSM using the -o vdsm output mode (which end
106       users should not try to use directly).
107
108       You have to specify -o rhv and an -os option that points to the RHV-M
109       Export Storage Domain.  You can either specify the NFS server and
110       mountpoint, eg. "-os rhv-storage:/rhv/export", or you can mount that
111       first and point to the directory where it is mounted, eg.
112       "-os /tmp/mnt".  Be careful not to point to the Data Storage Domain by
113       accident as that will not work.
114
115       On successful completion virt-v2v will have written the new guest to
116       the Export Storage Domain, but it will not yet be ready to run.  It
117       must be imported into RHV using the UI before it can be used.
118
119       In RHV ≥ 2.2 this is done from the Storage tab.  Select the export
120       domain the guest was written to.  A pane will appear underneath the
121       storage domain list displaying several tabs, one of which is "VM
122       Import".  The converted guest will be listed here.  Select the
123       appropriate guest an click "Import".  See the RHV documentation for
124       additional details.
125
126       If you export several guests, then you can import them all at the same
127       time through the UI.
128
129   Testing RHV conversions
130       If you do not have an oVirt or RHV instance to test against, then you
131       can test conversions by creating a directory structure which looks
132       enough like a RHV-M Export Storage Domain to trick virt-v2v:
133
134        uuid=`uuidgen`
135        mkdir /tmp/rhv
136        mkdir /tmp/rhv/$uuid
137        mkdir /tmp/rhv/$uuid/images
138        mkdir /tmp/rhv/$uuid/master
139        mkdir /tmp/rhv/$uuid/master/vms
140        touch /tmp/rhv/$uuid/dom_md
141        virt-v2v [...] -o rhv -os /tmp/rhv
142
143   Debugging RHV-M import failures
144       When you export to the RHV-M Export Storage Domain, and then import
145       that guest through the RHV-M UI, you may encounter an import failure.
146       Diagnosing these failures is infuriatingly difficult as the UI
147       generally hides the true reason for the failure.
148
149       There are several log files of interest:
150
151       /var/log/vdsm/import/
152           In oVirt ≥ 4.1.0, VDSM preserves the virt-v2v log file for 30 days
153           in this directory.
154
155           This directory is found on the host which performed the conversion.
156           The host can be selected in the import dialog, or can be found
157           under the "Events" tab in oVirt administration.
158
159       /var/log/vdsm/vdsm.log
160           As above, this file is present on the host which performed the
161           conversion.  It contains detailed error messages from low-level
162           operations executed by VDSM, and is useful if the error was not
163           caused by virt-v2v, but by VDSM.
164
165       /var/log/ovirt-engine/engine.log
166           This log file is stored on the RHV-M server.  It contains more
167           detail for any errors caused by the oVirt GUI.
168

SEE ALSO

170       virt-v2v(1).
171

AUTHOR

173       Richard W.M. Jones
174
176       Copyright (C) 2009-2019 Red Hat Inc.
177

LICENSE

179       This program is free software; you can redistribute it and/or modify it
180       under the terms of the GNU General Public License as published by the
181       Free Software Foundation; either version 2 of the License, or (at your
182       option) any later version.
183
184       This program is distributed in the hope that it will be useful, but
185       WITHOUT ANY WARRANTY; without even the implied warranty of
186       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
187       General Public License for more details.
188
189       You should have received a copy of the GNU General Public License along
190       with this program; if not, write to the Free Software Foundation, Inc.,
191       51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
192

BUGS

194       To get a list of bugs against libguestfs, use this link:
195       https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
196
197       To report a new bug against libguestfs, use this link:
198       https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
199
200       When reporting a bug, please supply:
201
202       ·   The version of libguestfs.
203
204       ·   Where you got libguestfs (eg. which Linux distro, compiled from
205           source, etc)
206
207       ·   Describe the bug accurately and give a way to reproduce it.
208
209       ·   Run libguestfs-test-tool(1) and paste the complete, unedited output
210           into the bug report.
211
212
213
214libguestfs-1.40.1                 2019-01-17            virt-v2v-output-rhv(1)
Impressum