Este conteúdo não está disponível no idioma selecionado.
4.3.2.6. Converting a VMware ESX / ESX(i) virtual machine
Important
virt-v2v -ic esx://esx.example.com/ -o rhev -os storage.example.com:/exportdomain --network rhevm guest_name
virt-v2v -ic esx://esx.example.com/ -o rhev -os storage.example.com:/exportdomain --network rhevm guest_name
storage.example.com:/exportdomain is the export storage domain, rhevm is the locally managed network to connect the converted virtual machine's network to, and guest_name is the name of the virtual machine.
--bridge parameter to connect to a locally managed network if your virtual machine only has a single network interface. If your virtual machine has multiple network interfaces, edit /etc/virt-v2v.conf to specify the network mapping for all interfaces.
Connecting to the ESX / ESX(i) server will require authentication. virt-v2v supports password authentication when connecting to ESX / ESX(i). It reads passwords from $HOME/.netrc. The format of this file is described in netrc(5). An example entry is:
machine esx.example.com login root password s3cr3t
machine esx.example.com login root password s3cr3t
Note
.netrc file must have a permission mask of 0600 to be read correctly by virt-v2v.
In non-production environments, the ESX / ESX(i) server may have a non-valid certificate, for example a self-signed certificate. In this case, certificate checking can be explicitly disabled by adding ?no_verify=1 to the connection URI as shown below:
... -ic esx://esx.example.com/?no_verify=1 ...
... -ic esx://esx.example.com/?no_verify=1 ...