[one-users] shutdown vm state

[Gary S. Cuozzo]

I guess I just never waited long enough. I went in and did a shutdown on one of my vm's and let it sit. It eventually went away and I was able to just redeploy the template and boot it back up. That makes much more sense. 

Thanks for the info. 

----- Original Message -----

From: "Ruben S. Montero" <rsmontero at opennebula.org> 
To: "Gary S. Cuozzo" <gary at isgsoftware.net> 
Cc: users at lists.opennebula.org 
Sent: Thursday, August 2, 2012 7:45:25 PM 
Subject: Re: [one-users] shutdown vm state 

VMs in done state are not show through sunstone or CLI, but kept in the DB for accounting purposes. You can check the history and stats of any VM (including those not shown, i.e.in done state). you can try it with onevm show <any_id_of_a_deleted_VM>. 


The default timeout for the shutdown operation is 5min, it can be change in the kvmrc file (you need to onehost sync if you change the default). 


You can check remotes/vmm/kvm/shutdown for specific information of the shutdown process. In this case we basically issue a shutdown operation and wait for the VM to not show up through libvirt. 


Cheers 


Ruben 



On Fri, Aug 3, 2012 at 1:29 AM, Gary S. Cuozzo < gary at isgsoftware.net > wrote: 




Ok. I've never seen any vm's hit the "DONE" state. At least not from the sunstone view. Maybe if I try the CLI to check the state I'd see it. My vm's just sit in the "shutdown" state where I just delete them. 

I have verified they do in fact shutdown properly. They do a clean shutdown via acpi and the vm instance (kvm) does go away on the host system. 

Thanks for the info. 



From: "Ruben S. Montero" < rsmontero at opennebula.org > 
To: "Gary S. Cuozzo" < gary at isgsoftware.net > 
Cc: users at lists.opennebula.org 
Sent: Thursday, August 2, 2012 4:12:23 PM 
Subject: Re: [one-users] shutdown vm state 

Hi, 


Maybe I am missing something. 


1.- SHUTDOWN is a transient state, the VM will end up in DONE, and so -*removed from the active list* or FAIL. So, there is no action to be taken from that state. You can delete it in case that somehow the process hangs. 


2.- From FAIL you can resubmit the VM preserving any resource (IP, image...). 


3.- Once the VM is DONE you can instantiate it again using the Template pool. 


4.- The VM may reach an UNKNOWN state, this happens when OpenNebula lost track of the VM for any reason. From that state you can start it up again, as the images are supposed to be already in the host. 


Hope now it is a bit clearer 


Cheers 


Ruben 



On Thu, Aug 2, 2012 at 8:39 PM, Gary S. Cuozzo < gary at isgsoftware.net > wrote: 

<blockquote>


Yes, the shutdown functions as I would expect. I'm just questioning why it seems to stay in the list of VM's when all I seem to be able to do is delete the VM. Granted the images are still there, so I can delete the VM, then recreate it again from the template. But it seems like it would be more useful if I could do something else, such as start it up again. I thought maybe I was missing something in the overall lifecycle picture, but maybe not. 



From: "Ruben S. Montero" < rsmontero at opennebula.org > 
To: "Gary S. Cuozzo" < gary at isgsoftware.net > 
Cc: users at lists.opennebula.org 
Sent: Thursday, August 2, 2012 1:28:28 PM 
Subject: Re: [one-users] shutdown vm state 

Hi 


Upon receiving the ACPI signal the VM should actually shutdown and then it will be removed from the hypervisor active list. From there OpenNebula will move around any persistent or save_as image. Check your guest OS for its ACPI configuration. 


There is a timeout for the shutdown operation, if the VM is still alive it will return to RUNNING. 


Cheers 


Ruben 


On Thu, Aug 2, 2012 at 6:04 PM, Gary S. Cuozzo < gary at isgsoftware.net > wrote: 

<blockquote>


Hello, 
I have a question about the shutdown state of a vm. Using ONE 3.6 and Sunstone GUI, if I click the "shutdown" button, the vm seems to do a clean shutdown via acpi and it stops running. The state is indicated as "SHUTDOWN". From there, the only thing I can seem to do is delete the VM. Any other action I attempt results in a wrong state error. 

What is the purpose and proper/intended use of the shutdown feature? 

Thanks, 
gary 


_______________________________________________ 
Users mailing list 
Users at lists.opennebula.org 
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org 







-- 
Ruben S. Montero, PhD 
Project co-Lead and Chief Architect 
OpenNebula - The Open Source Solution for Data Center Virtualization 
www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula 


_______________________________________________ 
Users mailing list 
Users at lists.opennebula.org 
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org 


</blockquote>




-- 
Ruben S. Montero, PhD 
Project co-Lead and Chief Architect 
OpenNebula - The Open Source Solution for Data Center Virtualization 
www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula 


_______________________________________________ 
Users mailing list 
Users at lists.opennebula.org 
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org 


</blockquote>




-- 
Ruben S. Montero, PhD 
Project co-Lead and Chief Architect 
OpenNebula - The Open Source Solution for Data Center Virtualization 
www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120802/b4d4c4f0/attachment-0002.htm>