1virt-v2v-output-rhv(1) Virtualization Support virt-v2v-output-rhv(1)
2
6 virt-v2v-output-rhv - Using virt-v2v to convert guests to oVirt or RHV
7
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-disk-uuid=UUID ...]
15 [-oo rhv-verifypeer]
16 virt-v2v [-i* options] -o rhv -os [esd:/path|/path]
18 virt-v2v [-i* options] -o vdsm
20 [-oo vdsm-image-uuid=UUID]
21 [-oo vdsm-vol-uuid=UUID]
22 [-oo vdsm-vm-uuid=UUID]
23 [-oo vdsm-ovf-output=DIR]
24
26 This page documents how to use virt-v2v(1) to convert guests to an
27 oVirt or RHV management instance. There are three output modes that
28 you can select, but only -o rhv-upload should be used normally, the
29 other two are deprecated:
30 -o rhv-upload -os STORAGE
32 Full description: "OUTPUT TO RHV"
33 This is the modern method for uploading to oVirt/RHV via the REST
35 API. It requires oVirt/RHV ≥ 4.2.
36 -o rhv -os esd:/path
38 -o rhv -os /path
39 Full description: "OUTPUT TO EXPORT STORAGE DOMAIN"
40 This is the old method for uploading to oVirt/RHV via the Export
42 Storage Domain (ESD). The ESD can either be accessed over NFS
43 (using the -os esd:/path form) or if you have already NFS-mounted
44 it somewhere specify the path to the mountpoint as -os /path.
45 The Export Storage Domain was deprecated in oVirt 4, and so we
47 expect that this method will stop working at some point in the
48 future.
49 -o vdsm
51 This is the old method used internally by the RHV-M user interface.
52 It is never intended to be used directly by end users.
53
55 This new method to upload guests to oVirt or RHV directly via the REST
56 API requires oVirt/RHV ≥ 4.2.
57 You need to specify -o rhv-upload as well as the following extra
59 parameters:
60 -oc "https://ovirt-engine.example.com/ovirt-engine/api"
62 The URL of the REST API which is usually the server name with
63 "/ovirt-engine/api" appended, but might be different if you
64 installed oVirt Engine on a different path.
65 You can optionally add a username and port number to the URL. If
67 the username is not specified then virt-v2v defaults to using
68 "admin@internal" which is the typical superuser account for oVirt
69 instances.
70 -of raw
72 Currently you must use -of raw and you cannot use -oa preallocated.
73 These restrictions will be loosened in a future version.
75 -op password-file
77 A file containing a password to be used when connecting to the
78 oVirt engine. Note the file should contain the whole password,
79 without any trailing newline, and for security the file should have
80 mode 0600 so that others cannot read it.
81 -os "ovirt-data"
83 The storage domain.
84 -oo rhv-cafile=ca.pem
86 The ca.pem file (Certificate Authority), copied from
87 /etc/pki/ovirt-engine/ca.pem on the oVirt engine.
88 If -oo rhv-verifypeer is enabled then this option can be used to
90 control which CA is used to verify the client’s identity. If this
91 option is not used then the system’s global trust store is used.
92 -oo rhv-cluster="CLUSTERNAME"
94 Set the RHV Cluster Name. If not given it uses "Default".
95 -oo rhv-disk-uuid="UUID"
97 This option can used to manually specify UUIDs for the disks when
98 creating the virtual machine. If not specified, the oVirt engine
99 will generate random UUIDs for the disks. Please note that:
100 • you must pass as many -oo rhv-disk-uuid=UUID options as the
102 amount of disks in the guest
103 • the specified UUIDs must not conflict with the UUIDs of
105 existing disks
106 -oo rhv-direct
108 If this option is given then virt-v2v will attempt to directly
109 upload the disk to the oVirt node, otherwise it will proxy the
110 upload through the oVirt engine. Direct upload requires that you
111 have network access to the oVirt nodes. Non-direct upload is
112 slightly slower but should work in all situations.
113 -oo rhv-verifypeer
115 Verify the oVirt/RHV server’s identity by checking the server‘s
116 certificate against the Certificate Authority.
117
119 This section only applies to the -o rhv output mode. If you use
120 virt-v2v from the RHV-M user interface, then behind the scenes the
121 import is managed by VDSM using the -o vdsm output mode (which end
122 users should not try to use directly).
123 You have to specify -o rhv and an -os option that points to the RHV-M
125 Export Storage Domain. You can either specify the NFS server and
126 mountpoint, eg. "-os rhv-storage:/rhv/export", or you can mount that
127 first and point to the directory where it is mounted, eg.
128 "-os /tmp/mnt". Be careful not to point to the Data Storage Domain by
129 accident as that will not work.
130 On successful completion virt-v2v will have written the new guest to
132 the Export Storage Domain, but it will not yet be ready to run. It
133 must be imported into RHV using the UI before it can be used.
134 In RHV ≥ 2.2 this is done from the Storage tab. Select the export
136 domain the guest was written to. A pane will appear underneath the
137 storage domain list displaying several tabs, one of which is "VM
138 Import". The converted guest will be listed here. Select the
139 appropriate guest an click "Import". See the RHV documentation for
140 additional details.
141 If you export several guests, then you can import them all at the same
143 time through the UI.
144 Testing RHV conversions
146 If you do not have an oVirt or RHV instance to test against, then you
147 can test conversions by creating a directory structure which looks
148 enough like a RHV-M Export Storage Domain to trick virt-v2v:
149 uuid=`uuidgen`
151 mkdir /tmp/rhv
152 mkdir /tmp/rhv/$uuid
153 mkdir /tmp/rhv/$uuid/images
154 mkdir /tmp/rhv/$uuid/master
155 mkdir /tmp/rhv/$uuid/master/vms
156 touch /tmp/rhv/$uuid/dom_md
157 virt-v2v [...] -o rhv -os /tmp/rhv
158 Debugging RHV-M import failures
160 When you export to the RHV-M Export Storage Domain, and then import
161 that guest through the RHV-M UI, you may encounter an import failure.
162 Diagnosing these failures is infuriatingly difficult as the UI
163 generally hides the true reason for the failure.
164 There are several log files of interest:
166 /var/log/vdsm/import/
168 In oVirt ≥ 4.1.0, VDSM preserves the virt-v2v log file for 30 days
169 in this directory.
170 This directory is found on the host which performed the conversion.
172 The host can be selected in the import dialog, or can be found
173 under the "Events" tab in oVirt administration.
174 /var/log/vdsm/vdsm.log
176 As above, this file is present on the host which performed the
177 conversion. It contains detailed error messages from low-level
178 operations executed by VDSM, and is useful if the error was not
179 caused by virt-v2v, but by VDSM.
180 /var/log/ovirt-engine/engine.log
182 This log file is stored on the RHV-M server. It contains more
183 detail for any errors caused by the oVirt GUI.
184
186 virt-v2v(1).
187
189 Richard W.M. Jones
190
192 Copyright (C) 2009-2020 Red Hat Inc.
193
195 This program is free software; you can redistribute it and/or modify it
196 under the terms of the GNU General Public License as published by the
197 Free Software Foundation; either version 2 of the License, or (at your
198 option) any later version.
199 This program is distributed in the hope that it will be useful, but
201 WITHOUT ANY WARRANTY; without even the implied warranty of
202 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
203 General Public License for more details.
204 You should have received a copy of the GNU General Public License along
206 with this program; if not, write to the Free Software Foundation, Inc.,
207 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
208
210 To get a list of bugs against libguestfs, use this link:
211 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
212 To report a new bug against libguestfs, use this link:
214 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
215 When reporting a bug, please supply:
217 • The version of libguestfs.
219 • Where you got libguestfs (eg. which Linux distro, compiled from
221 source, etc)
222 • Describe the bug accurately and give a way to reproduce it.
224 • Run libguestfs-test-tool(1) and paste the complete, unedited output
226 into the bug report.
227virt-v2v-1.45.91 2021-11-23 virt-v2v-output-rhv(1)