[Openstack] Help, How to restore existing vms after host reboot?

Razique Mahroua razique.mahroua at gmail.com
Mon Mar 12 14:45:12 UTC 2012


Mmmm,
I myself think it's not a good idea if you have an attached volume (via nova-volume)
Virsh rely on a disk-path populated via the open-iscsi component - thus an inactive session (after an host reboot) will likely prevent the domain from starting. 
the only dirty workaround I found so far is to redefine the domain before restarting it : 
# virsh undefine my_domain
# virsh define /var/lib/nova/instances/my_domain/libvirt.xml

I worked on that problematic few months back - you can also save the iscsi sessions, and make sure you restore them before - the only thing is to make sure iscsi sessions mount up before libvirt and nova-compute start 
#1 - openiscsi
#2- libvirt
#3- nova-compute

Nuage & Co - Razique Mahroua 
razique.mahroua at gmail.com



Le 12 mars 2012 à 15:14, Christian Wittwer a écrit :

> 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 <vishvananda at 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 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
>> 
> 
> _______________________________________________
> 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/20120312/4404d635/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/20120312/4404d635/attachment.jpg>


More information about the Openstack mailing list