cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-600) When rebooting KVM local storage VM host, libvirt definitions deleted
Date Fri, 04 Jan 2013 00:50:13 GMT


Marcus Sorensen commented on CLOUDSTACK-600:

The fact that there is no definition for the VMs in libvirt is by design, it won't survive
a reboot as they're not persistent. When a rebooted host comes back online, it will attempt
to stop any VMs that were previously running on that host, in case they were migrated away.
This often fails and results in the 'Domain not found' errors you mention, but it's just a

So the issue you're having, based on the symptoms you mention, is that:

1) KVM Host is rebooted
2) VMs on that host show up as 'stopped' in the management UI
3) when KVM Host comes back and shows 'connected' in the management UI, you are unable to
start the stopped VMs

You are using local storage, is there anything else that you can tell us about the environment?
Can you put the agent into debug mode (edit /etc/cloud/agent/log4j.xml and replace INFO with
DEBUG everywhere, then restart agent), then capture just the section out of /var/log/cloud/agent/agent.log
where attempting to start a VM fails?
> 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
>            Reporter: Andrew Bayer
> 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