cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-600) When rebooting KVM local storage VM host, libvirt definitions deleted
Date Fri, 15 Mar 2013 14:02:15 GMT


ASF subversion and git services commented on CLOUDSTACK-600:

Commit 6df107bcf6439c1de8346bc8b5c6be93694d9ee4 in branch refs/heads/4.1 from Chip Childers
[;h=6df107b ]

Summary: KVM - undefine persistent VMs on stop

Detail: A previous patch fixed an issue where we are defining VMs to persist
locally on KVM hosts, which can cause issues if the agent isn't running and
libvirt decides to start the VM unbeknownst to cloudstack. The previous patch
stopped defining VMs as persistent. This patch adds compatibility for existing
cloudstack environments, removing the persistent definition on stop if needed.

Signed-off-by: Marcus Sorensen <> 1363194656 -0600

> When rebooting KVM local storage VM host, libvirt definitions deleted
> ---------------------------------------------------------------------
>                 Key: CLOUDSTACK-600
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: pre-4.0.0, 4.1.0
>            Reporter: Andrew Bayer
>            Assignee: Marcus Sorensen
>             Fix For: 4.1.0, 4.2.0
> This is definitely the case in 3.0.3, and I don't think the relevant code has been touched
> When you reboot a VM host running KVM local storage VMs, the VMs are deleted from libvirt.
I presume this is due to CloudStack thinking it's migrating them away from the host, but obviously,
given that we're on local storage, it's unable to do that. The result is that the VMs are
not able to be restarted when the host comes back online.

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:

View raw message