Hi Robi Have you considered the rolling upgrade procedure ?
https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/hosts.html#kvm-rolling-maintenance https://www.shapeblue.com/cloudstack-feature-first-look-kvm-rolling-maintenance/ Can you share the agent logs (/var/log/cloudstack/agent.log) from the source host and destination host We may need to check for migration related exceptions Regards Kiran On Tue, Apr 7, 2026 at 12:22 PM Robi Setia Permadi <[email protected]> wrote: > Hallo Kiran, > > Yes, I understand that ideally all kvm hosts in a cluster should run the > same agent version. > However, in larger environments (e.g. hundreds of hosts), upgrades are > usually done in batches, so mixed versions are unavoidable during the > upgrade process. > > Is there any recommended workaround for this, or is live migration between > mixed agent versions not supported (i.e. no backward compatibility) ? > > Regards, > Robi > > On Tue, Apr 7, 2026 at 11:53 AM Kiran Chavala <[email protected]> > wrote: > > > Hi Robi > > > > Ideally on all the kvm hosts in a cluster should run the same agent > > version > > > > > > > https://docs.cloudstack.apache.org/en/4.22.0.0/installguide/hypervisor/kvm.html#host-kvm-installation > > > > > https://docs.cloudstack.apache.org/en/4.22.0.0/upgrading/upgrade/upgrade-4.22.html#kvm-on-centos-rhel > > > > Regards > > Kiran > > > > On Tue, Apr 7, 2026 at 4:00 AM Robi Setia Permadi < > [email protected] > > > > > wrote: > > > > > Hi All, > > > > > > 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:23:02 Marty Godsey wrote: > > > > Hello Again. > > > > > > > > I can start a VM on any host, but when I try to do a live migration I > > get > > > the following error: > > > > > > > > Provided libvirt destination ip is invalid > > > > > > > > Everything can be pinged, resolved, etc. The vm has the qemu agent > > > installed, all seems good. DNS is setup properly, the data base has the > > > correct IPs, the management label is set correctly, etc. > > > > > > > > It seems to be falling on this step: > > > > > > > > createMigrationURI > > > > > > > > I am running 4.20.1.0 on the server and a 4.21.0.0 agent? Could this > be > > > the issue? > > > > > > > > I do need to update to 4.20.1.0. > > > > > > > > > > > > * > > > > Marty > > > > > > > > > > > > > > > > > > > > > >
