VM poweroff instead of migration

[petr108m]

solution was here

Problem with migrating vms after host error hook launched

It seems that there is a bug that causes the VM to change to running state when disk monitoring arrives. I’ve opened an issue: https://dev.opennebula.org/issues/5331 EXECUTE SUCCESS 1 error: means that the hook was successfully executed and wrote no error message The VM changed from UNKNOWN to RUNNING before the scheduler picked it for rescheduling. That made it think it’s really running and tried to do a live migration. On UNKNOWN state the VM is not migrated, it’s redeployed. This was …