Re: [one-users] What are the causes let OpenNebula "thinks" VM is "POWEROFF" and how to recover?
Hi This problem is as described by Ondra becasue of a kind of race condition between the boot process and the monitor probes. You may or may not see it depending on timing network and the like. OpenNebula 4.10.2 includes some logic to deal with this and also to recover automatically the VM when its again monitored. What version are you running? Ruben On Fri Feb 13 2015 at 3:51:40 PM Hamada, Ondrej wrote: > Hi, > > I would suspect this to happen when the probe times out somehow (due to > the network issues etc.) or simply it cannot detect the VM at the moment. > Does the VM remain in ‘poweroff’ state forever or does it become ‘running’ > again after some time? > > > > Ondra > > > > *From:* Users [mailto:users-boun...@lists.opennebula.org] *On Behalf Of *Liu, > Gene > *Sent:* Friday, February 13, 2015 3:34 PM > *To:* users@lists.opennebula.org > *Subject:* [one-users] What are the causes let OpenNebula "thinks" VM is > "POWEROFF" and how to recover? > > > > 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 > -- > > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any > attachment and all copies and inform the sender. Thank you for > understanding. > ___ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] What are the causes let OpenNebula "thinks" VM is "POWEROFF" and how to recover?
Hi, I would suspect this to happen when the probe times out somehow (due to the network issues etc.) or simply it cannot detect the VM at the moment. Does the VM remain in 'poweroff' state forever or does it become 'running' again after some time? Ondra From: Users [mailto:users-boun...@lists.opennebula.org] On Behalf Of Liu, Gene Sent: Friday, February 13, 2015 3:34 PM To: users@lists.opennebula.org Subject: [one-users] What are the causes let OpenNebula "thinks" VM is "POWEROFF" and how to recover? 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 This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] What are the causes let OpenNebula "thinks" VM is "POWEROFF" and how to recover?
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
