[
https://issues.apache.org/jira/browse/CLOUDSTACK-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542747#comment-13542747
]
Marcus Sorensen commented on CLOUDSTACK-600:
--------------------------------------------
Are you sure this isn't just a misunderstanding in how cloudstack works?
Nothing regarding a VM host's libvirt information should be persistent. When a
storage pool is needed, cloudstack defines it. When a VM needs to be started,
cloudstack creates the XML definition on the fly and feeds it to libvirt. So
when a KVM host reboots and the network isn't accessible, or you say no VMs
exist, it's no surprise to me, as the management server has to tell the agent
which VMs exist and when to start them.
> When rebooting KVM local storage VM host, libvirt definitions deleted
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-600
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-600
> 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
> Reporter: Andrew Bayer
>
> This is definitely the case in 3.0.3, and I don't think the relevant code has
> been touched since.
> 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: http://www.atlassian.com/software/jira
