[Pkg-libvirt-commits] [libguestfs] 34/40: v2v: Copy -o rhev information from old virt-v2v manual page.

[Hilko Bengen]

This is an automated email from the git hooks/post-receive script.

bengen pushed a commit to annotated tag debian/1%1.27.57-1
in repository libguestfs.

commit d0110a4e239a978326b51dd79ca2b9abe30c1cb5
Author: Richard W.M. Jones <rjones at redhat.com>
Date:   Wed Oct 1 13:36:47 2014 +0100

    v2v: Copy -o rhev information from old virt-v2v manual page.
---
 v2v/virt-v2v.pod | 32 +++++++++++++++++++++++++++++++-
 1 file changed, 31 insertions(+), 1 deletion(-)

diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
index 491ed51..dd446ce 100644
--- a/v2v/virt-v2v.pod
+++ b/v2v/virt-v2v.pod
@@ -107,7 +107,7 @@ In this case the host running virt-v2v acts as a B<conversion server>.
 
 Note that after conversion, the guest will appear in the RHEV-M Export
 Storage Domain, from where you will need to import it using the RHEV-M
-user interface.
+user interface.  (See L</OUTPUT TO RHEV>).
 
 =head2 Convert disk image to OpenStack glance
 
@@ -347,6 +347,8 @@ I<-os> parameter must also be used to specify the location of the
 Export Storage Domain.  Note this does not actually import the guest
 into RHEV.  You have to do that manually later using the UI.
 
+See L</OUTPUT TO RHEV> below.
+
 =item B<-o vdsm>
 
 Set the output method to I<vdsm>.
@@ -870,6 +872,34 @@ Define the final guest in libvirt:
 
 =back
 
+=head1 OUTPUT TO RHEV
+
+This section only applies to the I<-o rhev> output mode.  If you use
+virt-v2v from the RHEV-M user interface, then behind the scenes the
+import is managed by VDSM using the I<-o vdsm> output mode (which end
+users should not try to use directly).
+
+You have to specify I<-o rhev> and an I<-os> option that points to the
+RHEV-M Export Storage Domain.  You can either specify the NFS server
+and mountpoint, eg. S<C<-os rhev-storage:/rhev/export>>, or you can
+mount that first and point to the directory where it is mounted,
+eg. S<C<-os /tmp/mnt>>.  Be careful not to point to the Data Storage
+Domain by accident as that will not work.
+
+On successful completion virt-v2v will have written the new guest to
+the Export Storage Domain, but it will not yet be ready to run.  It
+must be imported into RHEV using the UI before it can be used.
+
+In RHEV E<ge> 2.2 this is done from the Storage tab.  Select the
+export domain the guest was written to.  A pane will appear underneath
+the storage domain list displaying several tabs, one of which is "VM
+Import".  The converted guest will be listed here.  Select the
+appropriate guest an click "Import".  See the RHEV documentation for
+additional details.
+
+If you export several guests, then you can import them all at the same
+time through the UI.
+
 =head1 RUNNING VIRT-V2V AS ROOT OR NON-ROOT
 
 Nothing in virt-v2v inherently needs root access, and it will run just

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-libvirt/libguestfs.git