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

Posted to issues@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2014/01/27 20:26:39 UTC

[jira] [Closed] (CLOUDSTACK-5956) KVM vms still persisting in migration

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

Marcus Sorensen closed CLOUDSTACK-5956.
---------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 4.3.0)
                   Future

Pushed to master, will try to get cherry-picked into 4.3

> KVM vms still persisting in migration
> -------------------------------------
>
>                 Key: CLOUDSTACK-5956
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5956
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: Future
>
>
> VMs were moved to non-persistent about a year ago when there were issues with KVM hosts remembering which VMs were running on them after reboot, which disrupted HA and caused other bugs.  Migrations still set the persist flag on the migration destination, this is the last known place where VMs can persist. This was observed when trying to start an agent, the VM sync code kept reporting that there were vms that shouldn't be on the host and kept trying to stop them.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)