I've been running KVM public cloud up to recently and have never seen such
behaviour.
What versions (ACS, qemu, libvrit) are you running?
How does the migration fail - ACS job - or libvirt job?
destination VM is by default always in PAUSED state, until the migration is
finished - only then the
Hello Users
Recently we have seen cases where when the Vm migration fails, cloudstack
ends up running two instances of the same VM on different hypervisors. The
state will be "running" and not any other transition state. This will of
course lead to corruption of disk. Does CloudStack has any
