systemvm: vmware migration changes (#170)
* systemvm: vmware migration changes
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
* refactor systemvm storage migration note
Co-authored-by: Andrija Panic <45762285+andrijapanicsb@users.noreply.github.com>
Co-authored-by: Andrija Panic <45762285+andrijapanicsb@users.noreply.github.com>
diff --git a/source/adminguide/systemvm.rst b/source/adminguide/systemvm.rst
index a5e7f5e..062d6ea 100644
--- a/source/adminguide/systemvm.rst
+++ b/source/adminguide/systemvm.rst
@@ -812,6 +812,13 @@
.. |vr-upgrade.png| image:: /_static/images/vr-upgrade.png
:alt: Button to upgrade VR to use the new template.
+Migrating System VMs
+--------------------
+
+System VMs (any of the Console Proxy VM, Secondary Storage VM, Virtual Router or Load Balancer) can be migrated across hosts using migrateSysteVm API or migrate action in the UI. These VMs can be migrated between hosts of the same cluster only.
+
+Since CloudStack 4.16, for VMware, migration of System VMs can also be done to a destination host in a different cluster belonging to the same pod (in case of cluster-wide primary storage pools, this will cause the Root volume of the system VM to be migrated to the appropriate datastore in the new cluster). Storage migration of stopped System VMs is also supported.
+
Troubleshoot networks from System VMs
-------------------------------------
.. |run-diagnostics-icon.png| image:: /_static/images/run-diagnostics-icon.png
