You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/01/27 19:05:38 UTC
[jira] [Commented] (CLOUDSTACK-5956) KVM vms still persisting in
migration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883027#comment-13883027 ]
ASF subversion and git services commented on CLOUDSTACK-5956:
-------------------------------------------------------------
Commit daeea46da0fb7ba49d8c18334d9427fb9b06d524 in branch refs/heads/master from [~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=daeea46 ]
CLOUDSTACK-5956 remove persist flag during live migration
> 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: 4.3.0
>
>
> 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)