Op 07-04-2026 om 08:52 schreef Robi Setia Permadi:
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) ?
I agree with you that this should work. The culprit is this piece of
code:
https://github.com/apache/cloudstack/blob/main/plugins/hypervisors/kvm/src/main/java/com/cloud/hypervisor/kvm/resource/wrapper/LibvirtMigrateCommandWrapper.java#L99
if (StringUtils.isEmpty(destinationIp)) {
throw new CloudRuntimeException("Provided libvirt
destination ip is invalid");
}
So somehow the "destionationIp" variable is empty and this exception is
thrown.
That piece of code is already >5y old and probably nothing has changed
there.
Can't tell for sure why this is happening, but live migration between
agent versions is something which should work imho.
4.19 <> 4.22 might be a too big of a difference though.
That said: What are the Libvirt versions? Isn't there a difference there
and how the XML is presented by Libvirt?
Wido
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
