[pve-devel] [PATCH] add live storage migration doc

[Alexandre Derumier]

Signed-off-by: Alexandre Derumier <aderumier at odiso.com>
---
 qm.adoc | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/qm.adoc b/qm.adoc
index 02a4555..31e00a1 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -536,6 +536,15 @@ When your VM is running and it has no local resources defined (such as disks
 on local storage, passed through devices, etc.) you can initiate a live
 migration with the -online flag.
 
+If your VM have disks on local storage, you can migrate them to another 
+storage on target host (local or shared storage), with the flag :
+-with-local-disks flag.
+In this case, It'll try to migrate to target storage with same id than
+source storage.
+If you want to migrate to a target storage with a different id, you
+can add the flag : -targetstorage <yourtargetstorageid>
+
+
 How it works
 ^^^^^^^^^^^^
 
@@ -545,6 +554,11 @@ from the source Virtual Machine (since all other resources, e.g. disks,
 are shared, the memory content and device state are the only things left
 to transmit).
 
+If you have enabled local disk migration, an nbd server is started in the
+Qemu Process on target host. Then disk mirroring is done between source
+and target qemu process. When all disks on source and target are synced,
+the vm memory migration is starting.
+
 Once this connection is established, the source begins to send the memory
 content asynchronously to the target. If the memory on the source changes,
 those sections are marked dirty and there will be another pass of sending data.
@@ -557,7 +571,7 @@ Requirements
 
 For Live Migration to work, there are some things required:
 
-* The VM has no local resources (e.g. passed through devices, local disks, etc.)
+* The VM has no local resources (e.g. passed through devices, etc.)
 * The hosts are in the same {pve} cluster.
 * The hosts have a working (and reliable) network connection.
 * The target host must have the same or higher versions of the
-- 
2.11.0