Doc updates for rmigrate command

docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst

@@ -45,6 +45,31 @@ rpower fails with "Error: internal error: process exited while connecting to mon
 
      Then reboot the hypervisor...
 
+rmigrate fails with "Error: libvirt error code: 38, message: unable to connect to server at 'c910f05c35:49152': No route to host."
+----------------------------------------------------------------------------------------------------------------------------------
+
+   **Issue**: ::
+
+    #rmigrate vm1 kvmhost2
+    vm1: Error: libvirt error code: 38, message: unable to connect to server at 'kvmhost2:49152': No route to host: Failed migration of vm1 from kvmhost1 to kvmhost2
+
+   **Solution**:
+     Usually caused by active firewall. To disable the firewall issue: ::
+
+       systemctl disable firewalld
+
+rmigrate fails with "Error: 38, message: failed to create directory '<dir-name>': File exists: Unknown issue libvirt error code."
+---------------------------------------------------------------------------------------------------------------------------------
+
+   **Issue**: ::
+
+    #rmigrate vm1 kvmhost2
+    vm1: Error: 38, message: failed to create directory '<dir-name>': File exists: Unknown issue libvirt error code.
+
+   **Solution**:
+     Ususally happens when `nfs:` is specified for vmstorage attribute but that NFS directory is no longer mounted. Make sure the directory /var/lib/xcat/pools is empty on the destination kvmhost.
+
+
 Error: Cannot communicate via libvirt to kvmhost1
 -------------------------------------------------
 

docs/source/guides/admin-guides/references/man1/rmigrate.1.rst

@@ -36,6 +36,8 @@ For zVM:
 
 \ **rmigrate**\  requests that a guest VM to be moved from the current hypervisor to another.  It will request a live migration if possible.  The vmstorage directory should be shared between the source and destination hypervisors.
 
+Note: Make sure SELINUX is disabled and firewall is turned off on source and destination hypervisors.
+
 For zVM:
 ========
 
@@ -97,17 +99,29 @@ This is used to determine the current host to migrate from.
 
 1. To migrate kvm guest "kvm1" from hypervisor "hyp01" to hypervisor "hyp02", run:
 
-\ **rmigrate**\  \ *kvm1*\  \ *hyp02*\ 
+
+.. code-block:: perl
+
+  rmigrate kvm1 hyp02
+
 
 2. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is already on host "hyp02", enter:
 
-\ **rmigrate**\  \ *kvm1*\  \ *hyp02*\ 
+
+.. code-block:: perl
+
+  rmigrate kvm1 hyp02
+
 
 zVM specific:
 =============
 
 
 
-\ **rmigrate**\  \ *ihost123*\  destination=\ *pokdev62*\ 
+
+.. code-block:: perl
+
+  rmigrate ihost123 destination=pokdev62
+
 
 

xCAT-client/pods/man1/rmigrate.1.pod

@@ -12,7 +12,9 @@ B<rmigrate> I<noderange> [B<destination=>I<target_host>] [B<action=>I<action>] [
 
 =head1 B<Description>
 
-B<rmigrate> requests that a guest VM to be moved from the current hypervisor to another.  It will request a live migration if possible.  The vmstorage directory should be shared between the source and destination hypervisors.
+B<rmigrate> requests that a guest VM to be moved from the current hypervisor to another.  It will request a live migration if possible.  The vmstorage directory should be shared between the source and destination hypervisors. 
+
+Note: Make sure SELINUX is disabled and firewall is turned off on source and destination hypervisors.
 
 =head2 For zVM:
 
@@ -54,16 +56,16 @@ This is used to determine the current host to migrate from.
 
 1. To migrate kvm guest "kvm1" from hypervisor "hyp01" to hypervisor "hyp02", run:
 
-B<rmigrate> I<kvm1> I<hyp02>
+ rmigrate kvm1 hyp02
 
 2. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is already on host "hyp02", enter:
 
-B<rmigrate> I<kvm1> I<hyp02>
+ rmigrate kvm1 hyp02
 
 =head2 zVM specific:
 
 =over 4
 
-B<rmigrate> I<ihost123> destination=I<pokdev62>
+ rmigrate ihost123 destination=pokdev62
 
 =back