Beware of those flags though, since everytime you restart the nova-compute service, the running instances on it also reboot. For an autostart though $virsh autostart $domain would work. As for the auto-migration, that feature is not implemented actually Regards, Razique Mahroua - Nuage & Co razique.mahroua at gmail.com Tel : +33 9 72 37 94 15 Le 27 déc. 2012 à 12:03, JuanFra Rodriguez Cardoso <juanfra.rodriguez.cardoso at gmail.com> a écrit : > Hi: > > Two nova.conf flags can be useful for your case: > > --start_guests_on_host_boot=true > --resume_guests_state_on_host_boot=true > > Best Regards, > > JuanFra > > > 2012/12/26 Lei Zhang <zhang.lei.fly at gmail.com> > Hi all, > I am confused about how to do when the compute node is failed. For example, if the compute node reboot. I found the VMs on it didn't startup automatically. I must reboot the VMs manually. Is there any way to keep the HA? > In a bad situation, what should do if the node is crashed? How to keep the VMs migrate to other node automatically? > > > -- > Lei Zhang > > Blog: http://jeffrey4l.github.com > twitter/weibo: @jeffrey4l > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121227/c1c7bca7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: NUAGECO-LOGO-Fblan_petit.jpg Type: image/jpeg Size: 10122 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121227/c1c7bca7/attachment.jpg>