?
Solved

VMWARE VM starts global information

Posted on 2012-08-14
7
Medium Priority
?
665 Views
Last Modified: 2012-09-02
Hi,
Can someone explain to me how esxi5 works with auto starting virtual machine.
I am used to Microsoft virtual server and it clear and simple how it works: when you do a properties on a virtual machine, you have the Boot option with 1-don't boot, 2- previous states 3- always boot.
I don't see that in VMWare???

What happended this weekend was a power outage and only half of them rebooted not the other half. I have noticed that half of the servers successfully received a shutdown command from my MAIN UPS and the other half did not.
The half that received the shutdown and were cleanly shutdown did not reboot.
The half that did not received the shutdown and were forced shutdown all rebooted ok.

So looks like VMWare Boot option is setup by default to "As previous state".
So the server that were turn off right before the power outage never restarted.
0
Comment
Question by:SigSupport
  • 3
  • 2
5 Comments
 
LVL 124
ID: 38293774
do you have a VMware HA Cluster?

have you configured the VMs to Auto Start or Shutdown with host?

Im guessing but it would seem you could have VMware HA, which will restart VMs, that are Auto HA Protected when a host fails.

If VMs were shutdown manually, they are not HA protected because theynare OFF, and HA will not restart these automatically.

Auto Start and Shutdown Virtual Machines

Just log into your ESX server using the vSphere GUI Client, click on the host, then click the Configuration tab. In the 'Software' box, click the Virtual Machine Startup/Shutdown link. In the upper right click Properties.

http://www.vmadmin.co.uk/vmware/35-esxserver/111-esxautostartstop

However, it's not recommended to override, and set Auto Startup and Shutdown if you have VMware HA enabled.
0
 

Author Comment

by:SigSupport
ID: 38296125
Hi
Yes I have a HA cluster.
We have 4 blades in Cisco UCS chassis and all vm and ESX host boots from an EMC San.

The vm's that crash when the ups went down restarted when the power came back online so I guess HA restarted them when it notice they were forced shutdown.
But HA did not restart the VM's that were shutdown by Windows after receiving the UPS warning battery was low. Probably HA saw that these vm's were off and let them off??
So what to do for those. I went where you said on each blade esx configuration and I can see that the option "Start and Stop Virtual Machine with the system" is disable for all of them and all vm's are in the "Manual Startup" group.
If I turn this on and put it in the Auto-Start what would happens in the following case:
All my vm's can (and eventually would) move from one blade or another by VCenter for when resources is missing, when a blade fails etc... So when they are moved to another blade are they be put in the "Manual Startup" group by default?? I am afraid yes, so even if I moved them to the group "Autostart" now, if that settings gets lots every time a vm's gets moved to another blade then that's not good.
0
 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 38296353
But HA did not restart the VM's that were shutdown by Windows after receiving the UPS warning battery was low. Probably HA saw that these vm's were off and let them off??

This is the correct action for HA, because HA protection was not available because the VMs were OFF!

It's not recommended to use Auto Start with VMware HA, because the HA and VMs Auto Starting can conflict.
0
 

Author Comment

by:SigSupport
ID: 38347128
I've requested that this question be deleted for the following reason:

Did not find a way to put all VM in the "Start by default" position.
0
 
LVL 124
ID: 38347129
Im objecting because its not recommended by VMware, and overrides a design feature of HA.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Suggested Courses

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question