You can let nova-compute start the instances after a host reboot. --start_guests_on_host_boot --resume_guests_state_on_host_boot
2012/3/10 Vishvananda Ishaya <vishvana...@gmail.com>: > I think that this branch should make reboot work: > > https://review.openstack.org/#change,5177 > > It looks like we should also make sync_power_states run more frequently. It > currently runs every 6 minutes by default. > > On Mar 8, 2012, at 6:27 PM, DeadSun wrote: > > As we all know, if host reboot since of some failure or hardware problem, > the vms will actually shutoff. But after host up, info in nova db show vm > state are "active", and using "nova list" return the same. > > Now how to start the vms. In Daiblo, I always just using "nova reboot", it > works.But in essex version, it seems cannot use "nova reboot" in an inactive > domain. I see there is "nova host-action" command, but it not always make vm > start. > > Another way, I can use "virsh start" a domain, but if the vm attach a > volume, it doesn't work. "nova volume-detach" cannot detach a volume in an > inactive domain. > > Is there a normal way to resolve this case? > > -- > 非淡薄无以明志，非宁静无以致远 > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
