[
https://issues.apache.org/jira/browse/CLOUDSTACK-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388464#comment-14388464
]
Matty Courtney commented on CLOUDSTACK-8354:
--------------------------------------------
I've just noticed that the destoryVirtualMachine API operates the same way - it
tries to gracefully shutdown the guest OS rather than just powering off the VM.
If I'm destroying a VM I don't care if the guest shuts down gracefully.
> [VMware] restoreVirtualMachine should forcefully power off VM
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-8354
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8354
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, VMware
> Affects Versions: 4.4.2
> Reporter: Matty Courtney
> Priority: Minor
> Labels: vmware
>
> When restoreVirtualMachine API is called against a running instance
> CloudStack issues a command to vCenter to shutdown the guest OS, which shuts
> the OS down gracefully.
> Sometimes this graceful shutdown can take several minutes if there are
> processes that prevent/delay the OS shutting down gracefully.
> Presumably, when I call the restoreVirtualMachine API I don't care about the
> current state of the instance and nor do I care if it shuts down gracefully.
> Could the restoreVirtualMachine instead tell vCenter to Power Off the VM,
> which results in the VM immediately changing to a stopped state?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
