Hi,

I’m seeing a similar issue in my environment, here’s the exact scenario:

Setup:
- CloudStack Management: 4.22.0.0
- Agents: mix of 4.19.1.1 and 4.22.0.0

Migration results:
- 4.19 -> 4.22: fails
- 4.19 -> 4.19: fails
- 4.22 -> 4.22: works
- 4.22 -> 4.19: works

Error always happens at LibvirtMigrateCommandWrapper.createMigrationURI
with “Provided libvirt destination ip is invalid” error

Based on this behavior, it looks like migration depends on the source host
version.
Is there any workaround for this scenario, or is full agent version
alignment required?

Thanks.
Robi

On 2025/11/06 07:26:01 Wei ZHOU wrote:
> > I am running 4.20.1.0 on the server and a 4.21.0.0 agent? Could this be
> the issue?
>
> Yes, it could be the issue. You can upgrade to new 4.22.0.0 or use
4.20.2.0
>
>
> -Wei

Reply via email to