ESX 3.5 boots into maintenance mode and VM's sit idle.
When I power on my ESX3.5 host it automatically goes into maintenance mode.
I want it to go straight into production mode and boot the VM's on the host.
If we lose power to the server, when it is restored the ESX host will boot, but it wont boot all my virtualised MS servers otherwise we have to manually intervene to get things running. I really want it to all be automated so when power returns all systems get booted.
Any advice on how to do this much appreciated.
I want it to go straight into production mode and boot the VM's on the host.
If we lose power to the server, when it is restored the ESX host will boot, but it wont boot all my virtualised MS servers otherwise we have to manually intervene to get things running. I really want it to all be automated so when power returns all systems get booted.
Any advice on how to do this much appreciated.
Please update the build of the ESX version which you are currently using
ASKER
What does that mean.
I am using the latest versions, both shipped on cd to us within the last month and downloaded eval copy in the last week.
This will be a configuration issue not a patch issue I would have thought.
I am using the latest versions, both shipped on cd to us within the last month and downloaded eval copy in the last week.
This will be a configuration issue not a patch issue I would have thought.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
za mkh
Ok that actually works just the way I want it. This is me being really stupid as I had made it to that dialogue box and ticked the 'Automatically start stop Virtual Machines with the system' but failed to move the VM's into the start automatically field instead of manually.
Do you know about the shutdown procedure. If I select to go into maintenance mode or reboot or shutdown it warns me about VM's no longer running; will it at this point gracefully shutdown my VM's or just switch them off.
Points coming your way regardless, I'll shut question later.
Cheers
Jo
Ok that actually works just the way I want it. This is me being really stupid as I had made it to that dialogue box and ticked the 'Automatically start stop Virtual Machines with the system' but failed to move the VM's into the start automatically field instead of manually.
Do you know about the shutdown procedure. If I select to go into maintenance mode or reboot or shutdown it warns me about VM's no longer running; will it at this point gracefully shutdown my VM's or just switch them off.
Points coming your way regardless, I'll shut question later.
Cheers
Jo
ASKER
OK I did a little test.
I told VI Client to reboot the ESX server and no it didn't shutdown the VM's, it just killed them as they both reported unexpected shutdown when they came back up again.
Do you know a solution.
Cheers
Jo
I told VI Client to reboot the ESX server and no it didn't shutdown the VM's, it just killed them as they both reported unexpected shutdown when they came back up again.
Do you know a solution.
Cheers
Jo
Sorry for the late reply. Good to see that I have managed to help you so far.
In the configuration for Shutdown, ensure that the Shutdown action is Guest Shutdown
This will then do what you want it to do. But for guest shutdown to work you must ensure that each VM has the requisite VMWare tools installed.
Good luck!
In the configuration for Shutdown, ensure that the Shutdown action is Guest Shutdown
This will then do what you want it to do. But for guest shutdown to work you must ensure that each VM has the requisite VMWare tools installed.
Good luck!
ASKER
Za_mkh
Tested this and it works a treat. Thanks for help,feel happier with my setup now.
The manuals are useless, they say things like 'select one of the three options' without actually explaining what the options do.
Regards
Jo
Tested this and it works a treat. Thanks for help,feel happier with my setup now.
The manuals are useless, they say things like 'select one of the three options' without actually explaining what the options do.
Regards
Jo
A workaround we created was to create an alarm definition where when the guest system was off it would power back on. Only problem with this is, being that it is not production, sometimes we need to shut it off and it takes an extra step to do so.