cloudstack-dev mailing list archives

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


Andrew Bayer commented on CLOUDSTACK-600:

Ok, finally got a chance to play with a host with legitimate network problems. On reboot,
the VMs were running (in libvirt) but not in CloudStack. Trying to start them in CloudStack
would lead to errors and general confusion. Eventually, we restarted cloud-agent to turn on
debug logging - when it came back online, it undefined the VMs in libvirt, but left the storage
intact. A few minutes later, I tried relaunching an instance, and found it actually worked
this time. We need to duplicate this experience to figure out where exactly the issue is that's
keeping the instances from syncing up their state/coming back online automatically, but this
is definitely progress.
> 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