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 option of volume locking so that two instances of the same VM wont be running? Anyone else has faced this issue and found some solution to fix it? We are thinking of using "virtlockd" of libvirt or implementing custom lock mechanisms. There are some pros and cons of the both the solutions and i want your feedback before proceeding further. -- Thanks and regards Rakesh venkatesh
