<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think that this branch should make reboot work:<div><br></div><div><a href="https://review.openstack.org/#change,5177">https://review.openstack.org/#change,5177</a></div><div><br></div><div>It looks like we should also make sync_power_states run more frequently. It currently runs every 6 minutes by default.<br><div><div><br></div><div>On Mar 8, 2012, at 6:27 PM, DeadSun wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">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.<br>
<br>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.<br>
<br>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. <br><br>Is there a normal way to resolve this case?<br clear="all">
<br>-- <br>非淡薄无以明志，非宁静无以致远<br>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></body></html>