You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "terryye (JIRA)" <ji...@apache.org> on 2013/06/28 02:44:20 UTC

[jira] [Updated] (CLOUDSTACK-3222) One host node was crash ,the vm instance can not migrate to another host ,and the state is still running

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

terryye updated CLOUDSTACK-3222:
--------------------------------

    Summary: One host node was crash ,the vm instance can not migrate to another host ,and the state  is still running  (was: One host node was crash ,the vm instance can not migrate to another host ,and the state still is running)
    
> One host node was crash ,the vm instance can not migrate to another host ,and the state  is still running
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3222
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3222
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller, KVM, Management Server
>    Affects Versions: 4.1.0
>         Environment: ubuntu 12.04
>            Reporter: terryye
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> One host node was crash ,the vm instance can not migrate to another host ,and the state still is running
> When the node is recover,The vm state is running,but in  fact ,the vm is not running. it can not migrate,and restart. so i am modification the database , change state to stopped, the vm can start .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira