Skip to main content

How To Delay Auto Starting Virtual Machines In VMWare Server

How To Delay Auto Starting Virtual Machines In VMWare Server Running multiple Operating Systems as Virtual Machines has numerous advantages, until it comes time to reboot the Host Computer (running VMWare Server). You either need to manually start all VM's or allow them to startup at once causing a system wide bottleneck to occur on the Host.

Instead of trying to start up all VM's at once, you can configure VMWare Server to delay the startup times for each Virtual Machine, and specify the order in which each VM starts. In fact, an option also exist to auto shutdown each VM in a delayed ordered, making way for a more responsive Host during reboots.
For reasons unknown, you cannot configure delayed starting and shutdown of VM's using VMWare Server Console. Instead you need to use the web based VMWare Management Interface (VMI).
The Management Interface is installed during VMWare Server installation if it detects a Web Server (Apache or IIS) is installed. It can also be installed later by running VMWare Server setup again.
NOTE: if VMWare Management Interface will not connect when using IIS on Windows XP or Vista, see
starting the VMWare web service.
Once you have VMWare web service up and running, you can connect and logon to the interface by typing the following in your browser:
https://:8333 (or
https://localhost/:8333 when using the VMWare Host Computer)
If SSL is disabled, connect with
http://:8222
Enable Startup And Shutdown
Now that you are connected, first verify that all VM's Startup and Shutdown parameter have been enable (VM must be powered off to enable).
This can be set in the VMI by clicking on the down arrow (next to the VM icon),






followed by:
- Selecting Configure Options… - Click on Edit next to System Startup Options - Check Start Virtual Machine (set all other options as shown in below screenshot including Shutdown Options) - Click OK to save settingsNOTE: you can also set the delay time here, but as you will see later, it is much easier to set in the global System configuration section.










Setup Startup And Shutdown Delay Times

Once Startup and Shutdown has been enable for each VM, you can now set up the order and delay times by:
- Clicking on the Options tab from the main screen in VMI. Then click on Virtual Machine Startup and Shutdown… link.







- Followed by clicking on the Edit button in the System Configuration section.
In the System Startup and Shutdown Defaults screen, enable startup and shutdown by selecting the check box and set the delay times to your preference. Click OK to save settings.











Next set the order of starting each Virtual Machine, by editing the Specified Order or Any Order. Click OK to save settings.















Virtual Machines will shutdown in the reverse order you have configured for startup. When completed with the setup, you will see a summary of the settings and startup sequence similar to the below screen shot.















Now your VMWare Server host will more than likely see less bottlenecks and quicker startup and shutdown times. Also, with a graceful shutdown, your Virtual Machines will be less likely get corrupted from a hard shutdown (power off).

You can setup this option by editing the configuration file, Please refer the VMWare
Article:

Comments

Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires.
We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software.

This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment.
When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console.
Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager


Creating DSN

Create a System DSN for this d…

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only.

Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address)

~ # /ipmitool lan set 1 vlan id 333

~ # /ipmitool lan print1
Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : 255.255.254.0 MAC Address             : xx:xx:xx…

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called "vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format.

If you don’t have a VMotion/SVMotion license, use the following command to achieve the same.

From Thick to Thin:

vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk"

It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store.

Use the following command to see real-time usage of thin disk:

du –h "Thindisk.vmdk"

You can notice the big difference of disk usage between of Thin and Thick format disks.

From Thin to Thick:

vmkfstools –i "Thindisk.vmdk" -d zeroedthick "Thindisk…