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 17:08:12 GMT


Andrew Bayer commented on CLOUDSTACK-600:

Freed up a host and am doing some experiments. Rebooting the host while not in maintenance
mode but on the network etc resulted in the instance being suspended on shutdown, and then
on restart, cloud-agent failed to start, with:
Starting Cloud Agent: device virbr0-nic entered promiscuous mode
New device virbr0-nic does not support netpoll
Disabling netpoll for virbr0
virbr0: starting userspace STP failed, starting kernel STP
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ERROR. Could not send configure hw lro request
Ebtables v2.0 registered
ip6_tables: (C) 2000-2006 Netfilter Core Team
cloudbr0: port 1(eth2) entering forwarding state
The host name does not resolve properly to an IP address. Cannot start Cloud Agent.

...but libvirt resumed the instance just fine, and I was able to start cloud-agent at that
point, with no problems. Now trying to see what happens when I reboot with a disconnected
> 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