In CloudStack, stop means to power off the VM (with a force optional), destroy means to delete the VM.
It's sort of confusing, because 'destroy' tends to mean 'force shut down' in KVM/libvirt and Xen rather than deleting. On Tue, Oct 16, 2012 at 10:46 AM, Min Chen <min.c...@citrix.com> wrote: > Thanks Lee for clarification. Then my next natural question is: what is > the difference between stop instance and destroy instance (which are also > shown on CloudStack UI)? > > -min > > On 10/15/12 7:33 PM, "Gavin Lee" <gavin....@gmail.com> wrote: > >>It's by design, when you stop a VM (advanceStop() in >>VirtualMachineManagerImpl) in CloudStack UI, it will delete all the vm >>metadata info from xenserver database, it will reconstruct the vm >>profile to xenserver db when you start again (advanceStart() in >>VirtualMachineManagerImpl). >> >>It's easy to keep vm profile consistency since the only reference is >>cloudstack database. >> >>On Tue, Oct 16, 2012 at 6:12 AM, Min Chen <min.c...@citrix.com> wrote: >>> Hi there, >>> What did we internally invoke when user is stopping VM >>>instance from CloudStack UI? It seems that it did more than shutdown VM >>>from XenCenter. After this operation, my VM disappeared from XenCenter >>>console. If I manually do shutdown from XenCenter UI, I can see that my >>>VM is still there with stopped status. >>> Thanks >>> -min >> >> >> >>-- >>Gavin >
