tsinik-dw commented on issue #5924:
URL: https://github.com/apache/cloudstack/issues/5924#issuecomment-1041276392
Hi @nvazquez,
I tried a live VM migration from Xen to XCP. The destination host (XCP, Host
9 in log) is presented as expected in the UI along with the AutoSelect option.
I checked the XCP host as destination and tried the migration.
In the log I can see that _findHostsForMigration_ command is able to
identify the XCP host as a possible destination but the migration fails.
Management log attached
[live_intercluster_vm_migr_Xen70_to_Xcp82.txt](https://github.com/apache/cloudstack/files/8078394/live_intercluster_vm_migr_Xen70_to_Xcp82.txt)
Your guess is right!... Indeed, the API invoked is
_migrateVirtualMachineWithVolume_ instead of _migrateVirtualMachine_.
But, when the same migration tried using cmk the VM migration fails with the
following output:
~~~
(localcloud) 🐱 > migrate virtualmachine
virtualmachineid=c87de296-e0e4-4052-81a2-53798cfadd6c
hostid=73cd3fa4-01ce-4b55-970f-14efd0143aa1
cmd = org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd
jobstatus = 2
jobprocstatus = 0
jobresultcode = 530
accountid = 48ae3b86-8032-11ec-8660-4626a7ce6ce6
userid = 48bd974a-8032-11ec-8660-4626a7ce6ce6
created = 2022-02-16T10:07:28+0200
completed = 2022-02-16T10:07:30+0200
jobid = be5805f5-2330-4033-a314-bde52e666da2
jobresulttype = object
jobresult = map[errorcode:534 errortext:Resource [Host:9] is unreachable:
Host 9: Unable to prepare for migration due to Exception:
com.cloud.utils.exception.CloudRuntimeException
Message: There are 0 VMs named i-2-11-VM
Stack: com.cloud.utils.exception.CloudRuntimeException: There are 0 VMs
named i-2-11-VM
at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.prepareISO(CitrixResourceBase.java:4157)
at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixPrepareForMigrationCommandWrapper.execute(CitrixPrepareForMigrationCommandWrapper.java:59)
at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixPrepareForMigrationCommandWrapper.execute(CitrixPrepareForMigrationCommandWrapper.java:36)
at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1757)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
~~~
The corresponding management log during this cmk operation is attached too
[cmk_vm_migr_mgmt_log.txt](https://github.com/apache/cloudstack/files/8078397/cmk_vm_migr_mgmt_log.txt)
PS.1 I also tried to specify on cmk both hostid and storageid but got the
(expected): "Only one of hostId and storageId can be specified". Log available
if desired.
P.2 If I stop the VM on Xen cluster, then I can start it on the XCP cluster
as normal. This is easy for my test environment, but (almost) impossible in
production :-)
--
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]
