Hi Carlos. 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. Thank you!
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?? regards Marco On 02/11/2011 11:50 AM, Carlos Martín Sánchez wrote: > Hi, > > If I'm understanding right, you first log into your VM, shutdown it > yourself, and then issue the "onevm shutdown <id>". > Is this right? > > 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. > > If the VM Life Cycle is managed manually, OpenNebula will lose track > of what happened, that's why the VM is seen as UNKNOWN. > > Regards, > Carlos > -- > Carlos Martín, Engineer, MSc > Project Major Contributor > OpenNebula - The Open Source Toolkit for Cloud Computing > www.OpenNebula.org > <http://www.opennebula.org/> | cmar...@opennebula.org > <mailto:cmar...@opennebula.org> >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org