I think that's what it is supposed to do. It discards the old root disk and creates a fresh root disk for the vm and in case an optional field template id is passed in the root disk is created from this new template id. The api name is restoreVirtualMachine. Please check that the UI is internally invoking this api
Thanks, -Nitin On 19/03/14 1:55 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> wrote: >Hi, > >I noticed today while running through some test cases for 4.4 that >resetting a VM does not work as expected. > >Instead of the typical stop and re-start behavior where the VM is booted >back up using the same root disk, the VM gets a new root disk when it is >booted back up. > >Can anyone confirm this finding for me with his or her setup? > >Thanks! > >-- >*Mike Tutkowski* >*Senior CloudStack Developer, SolidFire Inc.* >e: mike.tutkow...@solidfire.com >o: 303.746.7302 >Advancing the way the world uses the >cloud<http://solidfire.com/solution/overview/?video=play> >*(tm)*
