<font color="#000000"><font><font face="courier new,monospace">Nice Vish !</font></font></font><div><font color="#000000"><font><font face="courier new,monospace">I dont know why i didnt see that in the docs, my bad.</font></font></font></div>
<div><font color="#000000"><font><font face="courier new,monospace"><br></font></font></font></div><div><font color="#000000"><font><font face="courier new,monospace">Thanks a lot!<br clear="all"></font></font></font><div>
<b>Alejandro</b></div>
<br><br><div class="gmail_quote">On Thu, Aug 30, 2012 at 7:28 PM, Vishvananda Ishaya <span dir="ltr"><<a href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">You want:<div>resume_guests_state_on_host_boot=true</div><div>start_guests_on_host_boot=false</div><div><br></div><div>The start_ option will essentially force a reboot every time nova is started, but the resume_ option will only attempt to reboot them if they are supposed to be running and the driver says they are not.</div>
<div><br></div><div>Vish</div><div><div class="h5"><div><br></div><div><div><div>On Aug 30, 2012, at 10:38 AM, Alejandro Comisario <<a href="mailto:alejandro.comisario@mercadolibre.com" target="_blank">alejandro.comisario@mercadolibre.com</a>> wrote:</div>
<br><blockquote type="cite"><font><font><font face="courier new,monospace">but what if still ... i want that if the compute node to autostart de vms if for any reason, it gets rebooted ? i dont want to start them by hand ( or issue an API reboot )</font></font></font><div>
<font><font><font face="courier new,monospace">Thats why i think it was great that this feature is managed ( at least in KVM ) from the libvirt side.</font></font></font></div><div><div><font><b><br></b></font></div>
<div><b>Alejandro</b></div>
<br><br><div class="gmail_quote">On Thu, Aug 30, 2012 at 1:59 PM, Alessandro Tagliapietra <span dir="ltr"><<a href="mailto:tagliapietra.alessandro@gmail.com" target="_blank">tagliapietra.alessandro@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Try to disable<br>
<br>
• # start_guests_on_host_boot=false<br>
<br>
in nova.conf, if nova-compute dies it doesn't means that the hypervisor is death.<br>
<br>
Il giorno 28/ago/2012, alle ore 04:42, Sam Su <<a href="mailto:susltd.su@gmail.com" target="_blank">susltd.su@gmail.com</a>> ha scritto:<br>
<div><div><br>
> Thanks for your guys help!<br>
> I guess this problem may be caused by nova packages auto upgrade.<br>
><br>
> I just found these two lines in the file /var/log/kern.log:<br>
> Aug 23 06:34:33 cnode-01 kernel: [4955691.256036] init: nova-network main process (9191) terminated with status 143<br>
> Aug 23 06:34:35 cnode-01 kernel: [4955693.402082] init: nova-compute main process (9275) terminated with status 143<br>
><br>
> Here is the link for detail of /var/log/kern.log<br>
> <a href="http://pastebin.com/GqH1ju1R" target="_blank">http://pastebin.com/GqH1ju1R</a><br>
><br>
> Also found these info in /var/log/dpkg.log:<br>
> 2012-08-23 06:34:33 upgrade nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012.1+stable~20120612-3ee026e-0ubuntu1.3<br>
> 2012-08-23 06:34:33 status half-configured nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:33 status unpacked nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:33 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:34 status triggers-pending ureadahead 0.100.0-12<br>
> 2012-08-23 06:34:34 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:34 status triggers-pending ureadahead 0.100.0-12<br>
> 2012-08-23 06:34:34 status triggers-pending man-db 2.6.1-2<br>
> 2012-08-23 06:34:34 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:34 status half-installed nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:34 status unpacked nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.3<br>
> 2012-08-23 06:34:34 status unpacked nova-network 2012.1+stable~20120612-3ee026e-0ubuntu1.3<br>
> 2012-08-23 06:34:34 upgrade nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012.1+stable~20120612-3ee026e-0ubuntu1.3<br>
> 2012-08-23 06:34:34 status half-configured nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:35 status unpacked nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:35 status half-installed nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:35 status half-installed nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.2<br>
> 2012-08-23 06:34:35 status unpacked nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.3<br>
> 2012-08-23 06:34:35 status unpacked nova-compute-kvm 2012.1+stable~20120612-3ee026e-0ubuntu1.3<br>
> 2012-08-23 06:34:35 upgrade nova-compute 2012.1+stable~20120612-3ee026e-0ubuntu1.2 2012.1+stable~20120612-3ee026e-0ubuntu1.3<br>
><br>
> Here is detail:<br>
> <a href="http://pastebin.com/juiSxCue" target="_blank">http://pastebin.com/juiSxCue</a><br>
><br>
> But I am not 100% sure of this. Does anyone knows what it means that a process was terminated with status 143 in Ubuntu 12.04?<br>
><br>
> Thanks ahead,<br>
> Sam<br>
><br>
><br>
> On Mon, Aug 27, 2012 at 5:56 PM, Alejandro Comisario <<a href="mailto:alejandro.comisario@mercadolibre.com" target="_blank">alejandro.comisario@mercadolibre.com</a>> wrote:<br>
> One of the things i dont like in essex.<br>
> That the "autostart" flag in nova.conf with KVM doesnt work with the autostart feature of libvirt/kvm, so if, for some reason you need to restart nova-compute to apply some kind of modification, the instances get soft/hard rebooted because now nova-compute handles the "autostart" flag from nova.conf<br>
><br>
> Why is that if some one can explain ?<br>
><br>
> On Mon, Aug 27, 2012 at 9:21 PM, Gabe Westmaas <<a href="mailto:gabe.westmaas@rackspace.com" target="_blank">gabe.westmaas@rackspace.com</a>> wrote:<br>
> Hey Sam,<br>
><br>
><br>
><br>
> Is it possible your hypervisors restarted? I see this entry in the logs:<br>
><br>
><br>
><br>
> 2012-08-23 06:35:02 INFO nova.compute.manager [req-f1598257-3f35-40e6-b5aa-d47a0e93bfba None None] [instance: ce00ff1d-cf46-44de-9557-c5a0f91c8d67] Rebooting instance after nova-compute restart.<br>
><br>
><br>
><br>
> Gabe<br>
><br>
><br>
><br>
> From: openstack-bounces+gabe.westmaas=<a href="mailto:rackspace.com@lists.launchpad.net" target="_blank">rackspace.com@lists.launchpad.net</a> [mailto:<a href="mailto:openstack-bounces%2Bgabe.westmaas" target="_blank">openstack-bounces+gabe.westmaas</a>=<a href="mailto:rackspace.com@lists.launchpad.net" target="_blank">rackspace.com@lists.launchpad.net</a>] On Behalf Of Sam Su<br>
> Sent: Monday, August 27, 2012 8:10 PM<br>
> To: openstack<br>
> Subject: [Openstack] HELP: All instances automatically rebooted.<br>
><br>
><br>
><br>
> Hi,<br>
><br>
><br>
><br>
> I have an Essex cluster with 6 compute nodes and one control nodes. All compute nodes are working not any interrupted, for some reason all instances in my cluster automatically rebooted. I am trying to but not figured out why this happened in these couple of days.<br>
><br>
><br>
><br>
> It's much appreciated if someone can give me some hints about how to deal with this situation.<br>
><br>
><br>
><br>
> Logs in my /var/log/upstart/nova-compute.log:<br>
><br>
> <a href="http://pastebin.com/WYJtS5a5" target="_blank">http://pastebin.com/WYJtS5a5</a><br>
><br>
><br>
><br>
> Let me know if need more info.<br>
><br>
><br>
> TIA,<br>
><br>
> Sam<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Alejandro<br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote></div><br></div></div></div></div></blockquote></div><br></div>