Merge pull request #27004 from apinnick/cnv-rhv-vm-id

BZ1894051: Getting RHV VM ID

Author: bergerhoffer

modules/virt-importing-vm-cli.adoc

@@ -160,7 +160,7 @@ EOF
 ----
 <1> If you create a ResourceMapping CR, uncomment the `resourceMapping` section.
 <2> Specify the target VM name.
-<3> The UUID of the source VM. If you specify the source VM ID, for example, `80554327-0569-496b-bdeb-fcbbf52b827b`, the source VM name and cluster are ignored. Alternatively, you can specify the source VM name and cluster.
+<3> Specify the source VM ID, for example, `80554327-0569-496b-bdeb-fcbbf52b827b`. You can obtain the VM ID by entering `\https://<RHV_Manager_FQDN>/ovirt-engine/api/vms/` in a web browser on the Manager machine to list all VMs. Locate the VM you want to import and its corresponding VM ID. You do not need to specify a VM name or cluster name.
 <4> If you specify the source VM name, you must also specify the source cluster. Do not specify the source VM ID.
 <5> If you specify the source cluster, you must also specify the source VM name. Do not specify the source VM ID.
 <6> If you create a ResourceMapping CR, comment out the `mappings` section.
@@ -169,7 +169,7 @@ EOF
 <9> If `storageMappings` are specified in both the ResourceMapping and the VirtualMachineImport CRs, the VirtualMachineImport CR takes precedence.
 <10> Specify the source storage domain.
 <11> Specify the target storage class.
-<12> Specify the source VM disk UUID, for example, `8181ecc1-5db8-4193-9c92-3ddab3be7b05`.
+<12> Specify the source VM disk ID, for example, `8181ecc1-5db8-4193-9c92-3ddab3be7b05`. You can obtain the disk ID by entering `\https://<RHV_Manager_FQDN>/ovirt-engine/api/vms/<VM_ID>` in a web browser on the Manager machine and reviewing the VM details.
 <13> Specify the target storage class.
 
 . Follow the progress of the virtual machine import to verify that the import was successful: