Replies: 2 comments 2 replies
-
@sourceYan , migrations across different storage solutions don’t always work great. It might well be that yours isn’ t supported. |
Beta Was this translation helpful? Give feedback.
1 reply
-
this is a known limitation I think for vm live mirgation between ceph storages, we should migrate the volume instead of the vm (it will use "virsh blockcopy"). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi cloudstack Community,
we do some tests with cloudstack and ceph.
Create the primary ceph storage is no problem, offline migration works also good!
But if i want do move a VM from or to ceph, i got the following error:
Failed to migrate VM [VM instance {"id":10,"instanceName":"i-2-10-VM","type":"User","uuid":"ff8ae527-bd26-4b74-b02c-8de21159ff01"}] along with its volumes due to [com.cloud.utils.exception.CloudRuntimeException: Copy volume(s) to storage(s) [{volume: "17", from: "7", to:"9"}] and VM to host [{vm: "10", from: "1", to:"4"}] failed in StorageSystemDataMotionStrategy.copyAsync. Error message: [Exception during migrate: org.libvirt.LibvirtException: Storage pool not found: no storage pool with matching target path '/var/log/cloudstack/management/cloudstack'].].
any ideas?
best regards!
YAN
Beta Was this translation helpful? Give feedback.
All reactions