On previous version of OpenNebula (4.12 and below) we could save a “hot” snapshot of a running machine with the command “onevm disk-snapshot --live […]”. It worked perfectly and quickly.
On OpenNebula 4.14 that command was replaced by “onevm disk-saveas”. But when using this new command, the new created disk is locked and it does not become Ready anymore (we wait over 2 days!)
There is any bug in this new command? How can we check log for the actions performed by “onevm disk-saveas” in order to check what’s happening?