virt-v2v
.
virt-v2v
:
-i input
|
Specifies the input method to obtain the guest for conversion. The default is libvirt. Supported options are:
|
-ic URI
|
Specifies the connection to use when using the libvirt input method. If omitted, this defaults to qemu:///system.
virt-v2v can currently automatically obtain guest storage from local libvirt connections, ESX connections, and connections over SSH. Other types of connection are not supported.
|
-o method
|
Specifies the output method. If no output method is specified, the default is libvirt. Supported output methods are:
|
-oc URI
|
Specifies the libvirt connection to use to create the converted guest. If omitted, this defaults to qemu:///system. Note that virt-v2v must be able to write directly to storage described by this libvirt connection. This makes writing to a remote connection impractical at present.
|
-os storage
|
Specifies the location where new storage will be created for the converted guest. This is dependent on the output method, specified by the
-o parameter.
For the libvirt output method, this must be the name of a storage pool. For the rhev output method, this specifies the NFS path to a Red Hat Enterprise Virtualization export storage domain. Note that the storage domain must have been previously initialized by the Red Hat Enterprise Virtualization Manager. The domain must be in the format <
host >:<path >. For example:
rhev-storage.example.com:/rhev/export
The NFS export must be mountable and writable by the host running virt-v2v.
|
-op pool
|
DEPRECATED Use
-os instead. This parameter is still supported, but is deprecated in favor of -os .
|
-osd domain
|
DEPRECATED Use
-os instead. This parameter is still supported, but is deprecated in favor of -os .
|
-of format
|
Specifies the on-disk format which will be used for the converted guest. Currently supported options are
raw and qcow2 . The output format does not need to be the same as the source format - virt-v2v can convert from raw to qcow2 and vice versa. If not specified, the converted guest will use the same format as the source guest.
|
-oa allocation
|
Specifies whether the converted guest should use
sparse or preallocated storage. The allocation scheme does not need to be the same as the source scheme - virt-v2v can convert from sparse to preallocated and vice versa. If not specified, the converted guest will use the same allocation scheme as the source.
|
-f file | --config file
| Load the virt-v2v configuration from file. Defaults to /etc/virt-v2v.conf if it exists. |
-n network | --network network
|
Map all guest bridges or networks which don't have a mapping in the configuration file to the specified network.
This option cannot be used in conjunction with --bridge.
|
-b bridge | --bridge bridge
|
Map all guest bridges or networks which don't have a mapping in the configuration file to the specified bridge.
This option cannot be used in conjunction with --network.
|
--help
| Display brief help. |
--version
| Display version number and exit. |