<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Setting order of machine startup after a crash or powerloss</title>
    <link>http://communities.vmware.com/community/vmtn/mgmt/vc?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Fri, 12 Dec 2008 13:59:02 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-12-12T13:59:02Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/1122645?tstart=0#1122645</link>
      <description>we had a similar outage where we had to restart every VM,  we also have a requirement to start some VMs in a particular order,  understand this can be scripted on a single host, but how can you script this across an entire ESX cluster?</description>
      <pubDate>Fri, 12 Dec 2008 13:59:02 GMT</pubDate>
      <author>kklueber</author>
      <guid>http://communities.vmware.com/message/1122645?tstart=0#1122645</guid>
      <dc:date>2008-12-12T13:59:02Z</dc:date>
      <clearspace:dateToText>11 months, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/927976?tstart=0#927976</link>
      <description>&lt;br /&gt;
yes but you do it just 1 time (in general) and you can always create it in a perl script of strating the machines in your order...&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Mon, 28 Apr 2008 10:59:32 GMT</pubDate>
      <author>VBarak</author>
      <guid>http://communities.vmware.com/message/927976?tstart=0#927976</guid>
      <dc:date>2008-04-28T10:59:32Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/927992?tstart=0#927992</link>
      <description>&lt;br /&gt;
This might be almost the thing I'm looking for, at least for the moment.&lt;br /&gt;
&lt;p /&gt;
It limits me to three levels, and they it would be "bios delay" that would have to be used. &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
I would realy like to be able to do a "flowchart" with machine dependencies in VC.&lt;br /&gt;
&lt;p /&gt;
Both to help to start the machines and to easily document it.&lt;br /&gt;
&lt;p /&gt;
We have it on paper now, but as always that kind of information "rot" with time and changes.</description>
      <pubDate>Mon, 28 Apr 2008 10:52:24 GMT</pubDate>
      <author>Svedja</author>
      <guid>http://communities.vmware.com/message/927992?tstart=0#927992</guid>
      <dc:date>2008-04-28T10:52:24Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/927990?tstart=0#927990</link>
      <description>Usefull only with a few machines. To cumbersome for many machines.</description>
      <pubDate>Mon, 28 Apr 2008 10:48:16 GMT</pubDate>
      <author>Svedja</author>
      <guid>http://communities.vmware.com/message/927990?tstart=0#927990</guid>
      <dc:date>2008-04-28T10:48:16Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/927975?tstart=0#927975</link>
      <description>&lt;br /&gt;
(under configuration&amp;gt;&amp;gt; VM startup/shutdown).&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
this is good for a non-clustered (HA\DRS) environment..&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
in HA environments you need to configure the priorities of your server (low\med\high) and the HA will start them from high to low...</description>
      <pubDate>Mon, 28 Apr 2008 10:40:15 GMT</pubDate>
      <author>VBarak</author>
      <guid>http://communities.vmware.com/message/927975?tstart=0#927975</guid>
      <dc:date>2008-04-28T10:40:15Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/927957?tstart=0#927957</link>
      <description>Hi,&lt;br /&gt;
&lt;br /&gt;
 You can set the automatic startup and shutdown in each ESX host (under configuration&amp;gt;&amp;gt; VM startup/shutdown). You can configure the startup and shutdown delay in that. This option can help u.&lt;br /&gt;
&lt;br /&gt;
Hope this helps &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;</description>
      <pubDate>Mon, 28 Apr 2008 10:24:35 GMT</pubDate>
      <author>Rajeev S</author>
      <guid>http://communities.vmware.com/message/927957?tstart=0#927957</guid>
      <dc:date>2008-04-28T10:24:35Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/927915?tstart=0#927915</link>
      <description>&lt;br /&gt;
Dont have a console in front of me at the moment but I cant remember if there is a way to do this, the only thing I could think of was in 3.5 there is a new feature which delays the BIOS screen, could you use this to your advantageby setting different delays on the servers ? &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;VM BIOS Delay&lt;/b&gt;&lt;br /&gt;
One new feature, VM BIOS Delay setting, is very handy if you are&lt;br /&gt;
trying to get to the Boot menu to boot from a CD-ROM. Prior to 3.5, the&lt;br /&gt;
VMware BIOS screen only showed for a &lt;i&gt;very&lt;/i&gt; brief second or two,&lt;br /&gt;
which made it difficult to get to the BIOS Setup Menu (F2) or Boot&lt;br /&gt;
Device Menu (ESC). You can now edit the VM's settings. &lt;br /&gt;
&lt;p /&gt;
There is a boot options selection under advanced on the&lt;br /&gt;
options tab, here you can set a power-on boot delay in&lt;br /&gt;
milli-seconds.</description>
      <pubDate>Mon, 28 Apr 2008 09:41:23 GMT</pubDate>
      <author>alanrenouf</author>
      <guid>http://communities.vmware.com/message/927915?tstart=0#927915</guid>
      <dc:date>2008-04-28T09:41:23Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Setting order of machine startup after a crash or powerloss</title>
      <link>http://communities.vmware.com/message/927842?tstart=0#927842</link>
      <description>&lt;br /&gt;
We had a major powerloss the other day (due to a human mistake) and our datacenter lost all it's power.&lt;br /&gt;
&lt;p /&gt;
After that we had to restart all of our machines, one by one.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
As it was weekend we didn't have our regular staff here, and as a result several machines were started in "wrong" order were ie database dependencies weren't fullfilled.&lt;br /&gt;
&lt;p /&gt;
Is there any way to tell VC in which order to start up machines? Preferably set order within a group av virtual machines (or resource-pools maybe?). &lt;br /&gt;
&lt;p /&gt;
The same could apply if an ESX machine crashes.</description>
      <pubDate>Mon, 28 Apr 2008 08:59:40 GMT</pubDate>
      <author>Svedja</author>
      <guid>http://communities.vmware.com/message/927842?tstart=0#927842</guid>
      <dc:date>2008-04-28T08:59:40Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
  </channel>
</rss>

