[GitHub] [cloudstack] tsinik-dw edited a comment on issue #5924: Xenserver/XCP-NG Inter-cluster VM migration with ROOT on managed storage

Fri, 18 Feb 2022 02:19:06 -0800 


tsinik-dw edited a comment on issue #5924:
URL: https://github.com/apache/cloudstack/issues/5924#issuecomment-1044278341


   Hi @nvazquez,
   
   just tried **successfully**  inter-cluster VM migration through UI using   
**cloudstack-common-4.17.0.0-SNAPSHOT.20220217.el7.x86_64.rpm, 
cloudstack-management-4.17.0.0-SNAPSHOT.20220217.el7.x86_64.rpm
   
   VM with `ROOT` disk on Solidfire and `DATA` disk on NFS migrated from XEN to 
XCP cluster choosing storage pool destination for each disk through the UI... 
just excellent! 
   
   Snapshots, and management log are following:
   ![2022-02-18 
11_46_15-Window](https://user-images.githubusercontent.com/87693561/154661762-fd8be046-cedb-4fd8-b288-63540580ab90.png)
   
   ![2022-02-18 
11_46_38-Window](https://user-images.githubusercontent.com/87693561/154661810-d3bef9d0-a9f8-4f40-8b7f-90724794b503.png)
   
   ![2022-02-18 
11_47_01-Window](https://user-images.githubusercontent.com/87693561/154661859-8fc5bc2f-fc1b-4ceb-97d1-dcd159c40a8c.png)
   
   ![2022-02-18 
11_47_45-Window](https://user-images.githubusercontent.com/87693561/154661910-cc50dd0f-c315-41b5-aa9b-2f6c08a7db5f.png)
   
   ![Inked2022-02-18 
11_57_38-Window_LI](https://user-images.githubusercontent.com/87693561/154662972-97d68486-cae3-4fe4-898a-9bbb8a3a11b6.jpg)
   
   ![Inked2022-02-18 
11_58_26-Window_LI](https://user-images.githubusercontent.com/87693561/154662996-20d4dfe5-73db-4ea0-b792-d002e98a1afb.jpg)
   
   
   Management log: 
[nv_intercluster-vm_migr_UI.txt](https://github.com/apache/cloudstack/files/8096243/nv_intercluster-vm_migr_UI.txt)
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to