[
https://issues.apache.org/jira/browse/CLOUDSTACK-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh resolved CLOUDSTACK-5463.
---------------------------------------
Resolution: Fixed
It was fixed in commit d45ee3ef21fd55c8a1cf1373225cab81389ad8c7 and
3ec7497e1ebcaa65a8cbd24c27326356355ac8cc; as part of vmsync changes. When a vm
is stopped outside cloudstack; say by Hyper-V manager; the state of the vm is
updated to stopped in cloudstack db too.
> Hyper-V does not report stopped VMs
> -----------------------------------
>
> Key: CLOUDSTACK-5463
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5463
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.3.0
> Reporter: Donal Lafferty
> Assignee: Devdeep Singh
> Labels: Hyper-V
> Fix For: 4.4.0
>
>
> The Hyper-V agent is never asked whether a VM is running. E.g. it is only
> asked the VmStats:
> 2013-12-11 06:28:08,544 [32] INFO HypervResource.HypervResourceController
> [7bbebc6a-400a-4d9f-832a-06924b823ba4] -
> com.cloud.agent.api.GetVmStatsCommand{
> "vmNames": [
> "i-2-3-VM"
> ],
> "hostGuid": "700b99d8-36e7-3f0c-b362-44f1c773241b-HypervResource",
> "hostName": "10.70.176.29",
> "contextMap": {},
> "wait": 0
> }
> 2013-12-11 06:28:08,716 [32] DEBUG HypervResource.WmiCallsV2
> [7bbebc6a-400a-4d9f-832a-06924b823ba4] - VM
> 20E0665F-4EE0-42A5-AC94-03DC9D3B5E8C(elementName i-2-3-VM) has 1 CPUs, and
> load of 0
> 2013-12-11 06:28:08,717 [32] INFO HypervResource.HypervResourceController
> [7bbebc6a-400a-4d9f-832a-06924b823ba4] - {
> "com.cloud.agent.api.GetVmStatsAnswer": {
> "vmStatsMap": {
> "i-2-3-VM": {
> "cpuUtilization": 0.0,
> "networkReadKBs": 1.0,
> "networkWriteKBs": 1.0,
> "numCPUs": 1,
> "entityType": "vm"
> }
> },
> "result": true,
> "contextMap": {}
> }
> }
> Therefore, if the VM shut itself down, the management server thinks it is
> still running.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
