<br><div class="gmail_quote">2011/2/11 Marco Strutz <span dir="ltr"><<a href="mailto:marco.strutz@desy.de">marco.strutz@desy.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
Hi Carlos.<br>
<br>
You have saved my day. I had a look at the acpi deamon inside my vm:
it wasn't running. As soon as I have repaired the configuration the
acpi signals were successfully passed into the machine and the
"onevm shutdown" works again.<br>
Thank you!<br>
<br></div></blockquote><div><br></div><div>I'm glad you solved it</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000">
Just for clarification: As soon as the vm shuts down by itself (for
whatever reason) opennebula has no chance to successfully run the
complete chain of the "saveas" workflow??<br>
<br>
<br></div></blockquote><div><br></div><div>That's right, OpenNebula assumes the VM Life Cycle is managed exclusively by itself.</div><div><br></div><div>If you want to be able to take the decision to shutdown the VM from the virtualized environment, you would have to make it contact the front-end where OpenNebula is running and use the command 'onevm shutdown <self-id>'</div>
<div><br></div><div>Regards,</div><div>Carlos</div><div><meta charset="utf-8"><br clear="all"><span style="border-collapse: collapse; color: rgb(136, 136, 136); font-family: arial, sans-serif; font-size: 13px; ">--<br>Carlos Martín, Engineer, MSc<br>
Project Major Contributor<br><span style="background-color: rgb(255, 255, 204); color: rgb(34, 34, 34); ">OpenNebula</span> - The Open Source Toolkit for Cloud Computing<br><a href="http://www.opennebula.org/" target="_blank" style="color: rgb(42, 93, 176); ">www.<span style="background-color: rgb(255, 255, 204); color: rgb(34, 34, 34); ">OpenNebula</span>.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank" style="color: rgb(42, 93, 176); ">cmartin@<span style="background-color: rgb(255, 255, 204); color: rgb(34, 34, 34); ">opennebula</span>.org</a></span><br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000">
regards<br><font color="#888888">
Marco</font><div class="im"><br>
<br>
On 02/11/2011 11:50 AM, Carlos Martín Sánchez wrote:
<blockquote type="cite">Hi,
<div><br>
</div>
<div>If I'm understanding right, you first log into your VM,
shutdown it yourself, and then issue the "onevm shutdown
<id>".</div>
<div>Is this right?</div>
<div><br>
</div>
<div>onevm shutdown command assumes the VM is still running, and
sends the ACPI signal to the machine. Your virtualized OS is
supposed to shutdown itself with this shutdown signal.</div>
<div><br>
</div>
<div>If the VM Life Cycle is managed manually, OpenNebula will
lose track of what happened, that's why the VM is seen as
UNKNOWN.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Carlos<br clear="all">
<span style="border-collapse:collapse;color:rgb(136, 136, 136);font-family:arial,sans-serif;font-size:13px">--<br>
Carlos Martín, Engineer, MSc<br>
Project Major Contributor<br>
<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34)">OpenNebula</span> - The Open Source
Toolkit for Cloud Computing<br>
<a href="http://www.opennebula.org/" style="color:rgb(42, 93, 176)" target="_blank">www.<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34)">OpenNebula</span>.org</a> | <a href="mailto:cmartin@opennebula.org" style="color:rgb(42, 93, 176)" target="_blank">cmartin@<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34)">opennebula</span>.org</a></span><br>
<br>
</div>
</blockquote>
<br>
</div></div>
</blockquote></div><br>