No announcement yet.

Startup and Shutdown Delay

  • Filter
  • Time
  • Show
Clear All
new posts

  • Startup and Shutdown Delay

    Under Virtual Machine Startup and Shutdown options, if I have a guest startup delay set at 60, does that mean it will
    1) wait 60 seconds and then start, or
    2) start and then wait 60 seconds until the next guest starts


  • #2
    Re: Startup and Shutdown Delay

    Assuming it is the same as HyperV it will start 60 seconds after the Host completes starting (or possibly the VM service starts)
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    IT Trainer / Consultant
    Ossian Ltd

    ** Remember to give credit where credit is due and leave reputation points where appropriate **


    • #3
      Re: Startup and Shutdown Delay

      You mean this:
      Technical Consultant

      MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
      "No matter how secure, there is always the human factor."

      "Enjoy life today, tomorrow may never come."
      "If you're going through hell, keep going. ~Winston Churchill"


      • #4
        Re: Startup and Shutdown Delay

        The link provided shows how to set the automatic startup options, but nowhere can I find an explanation of what the delays actually mean. You'd think the vSphere documentation would have an explanation, and it does elaborate on the automatic startup/shutdown options, but their explanations don't make any sense to me. For example:
        • If you want to allow virtual machines to start and stop automatically, click the check box at the top of the dialog box and enter a time in seconds for the default startup delay and the default shutdown delay.
        • If you want the operating system to start after a brief delay, specify a delay time in the Default Startup Delay box. This allows time for VMware Tools or the booting system to run scripts.
        • Click the check box if you want the operating system to boot immediately after VMware Tools starts.
        If I'm understanding the concepts correctly, VMware Tools is a set of utilities/drivers that runs on the guest VM in order to facilitate communication between the ESXi host and the VM. If that's true, then how could it be possible for VMware Tools or the booting system (guest VM, I'm assuming) to run anything, scripts or otherwise, BEFORE the guest OS is even booted?

        I'm asking because I thought I had configured the automatic startup/shutdown parameters correctly, but now and then after a reboot of the host OS (ESXi 5), the guest machines are reporting an unexpected shutdown.

        Can someone shed light on what these auto startup/shutdown parameters actually affect, and perhaps give a real-world example with some VMs that take more than a few minutes to boot up? (One of our guest machines is an SBS 2011 box, which takes a fair amount of time to shut down or start up since it's got Exchange, SharePoint, etc. all running)