cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devdeep Singh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-5463) Hyper-V does not report stopped VMs
Date Thu, 26 Dec 2013 06:14:51 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856775#comment-13856775
] 

Devdeep Singh commented on CLOUDSTACK-5463:
-------------------------------------------

Need to verify how other hypervisors behave when a vm is stopped outside cloudstack. Reducing
the priority from blocker to critical as it doesn't block qa validation.

> 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
>            Priority: Critical
>              Labels: Hyper-V
>
> 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.1.5#6160)

Mime
View raw message