Offline migration fails in SolusVM 2 if storage paths on Source and Destination Compute Resources are different: Could not open '/vz/vmprivate/221/0': No such file or directory

Symptoms 

Offline migration fails in SolusVM 2 if storage paths on Source and Destination Compute Resources are different:

SVM_ERROR: Cannot migrate VM "0df62c16-bd09-487f-a684-06be831bb123": prepare destination for migration: remove checkpoints for offline domain: remove all bitmaps from "/vz/vmprivate/221/0": failed to execute 'qemu-img info --output=json /vz/vmprivate/221/0' output: failed "qemu-img info --output=json /vz/vmprivate/221/0" with stdErr: "qemu-img: Could not open '/vz/vmprivate/221/0': Could not open '/vz/vmprivate/221/0': No such file or directory\n", stdOut: "", exitStatus: exit status 1

Cause

SolusVM 2 bug with ID #SIO-5573 which was fixed in SolusVM version 2.0.0-32302

Resolution

Update SolusVM 2 to the latest mainline version.