Opennebula 4.14 and disk-saveas command


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?

Thank you!

Does the log of the VM say anything?


This is a sample log file, as you can see no error/warnings detected:

Mon Nov 2 08:05:53 2015 [Z0][VM][I]: New LCM state is RUNNING
Mon Nov 2 08:08:41 2015 [Z0][VMM][I]: VM successfully rebooted-hard.
Tue Nov 3 00:00:26 2015 [Z0][VM][I]: New LCM state is HOTPLUG_SAVEAS

Best regards,


Sorry, I was our mistake.

The server has a secondary filesystem that was not properly mounted, so the server was “waiting” endlessly.

It works fine!.

Best regards,