Hi Everyone, Anyone had ever encounter an issue about VM stat changes to "POWEROFF" a few minutes (2 ~ 3 minutes) after "RUNNING"?
The actual problem is that the "POWEROFF" stat is incorrect as the VM is actually running on the computing node. If you try to "boot" it back, it will failed as that instance is already running on the same computing node. Is it a bug of OpenNebula? Any suggestions to get it recovered? Thanks, Gene ************************* VM log **************************************** Thu Feb 12 14:46:36 2015 [Z0][DiM][I]: New VM state is ACTIVE. Thu Feb 12 14:46:37 2015 [Z0][LCM][I]: New VM state is PROLOG. Thu Feb 12 14:49:43 2015 [Z0][LCM][I]: New VM state is BOOT Thu Feb 12 14:49:43 2015 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/42922/deployment.0 Thu Feb 12 14:49:43 2015 [Z0][VMM][I]: ExitCode: 0 Thu Feb 12 14:49:43 2015 [Z0][VMM][I]: Successfully execute network driver operation: pre. Thu Feb 12 14:49:46 2015 [Z0][VMM][I]: ExitCode: 0 Thu Feb 12 14:49:46 2015 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy. Thu Feb 12 14:49:46 2015 [Z0][VMM][I]: ExitCode: 0 Thu Feb 12 14:49:46 2015 [Z0][VMM][I]: Successfully execute network driver operation: post. Thu Feb 12 14:49:46 2015 [Z0][LCM][I]: New VM state is RUNNING Thu Feb 12 14:51:48 2015 [Z0][DiM][I]: New VM state is POWEROFF
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
