VMware Cloud Community
gjbird
Contributor
Contributor

Autostart fails to start machines after ESX reboot or power failure

Having problems with a new ESX install

One new ESX install in a test setup (old dell dual cpu)

Built several guests, and set some of them to autostart

Whether I reboot in maintenance mode, out of maintenance mode, at the console or by just pulling the power out of the back, the guests just will NOT autostart.

So far as I can see, everything is set correctly,

Help please

Thanks

Reply
0 Kudos
13 Replies
esiebert7625
Immortal
Immortal

Just to verify, even though you have it enabled for the VM you must enable it for the server by checking the "Allow virtual machines to start and stop automatically with the system" option

Reply
0 Kudos
gjbird
Contributor
Contributor

Only place I can see to set the options is

Virtual Inftastructure Client -> Select ESX Server -> configuration -> virtual machine startup/shutdown -> properties -> Allow virtual machines to start/stop automatically with the system (which is ticked)

Under that I then also have the startup order with 3 machines set to autostart

see http://www.gjbird.plus.com/esx/ for a screenshot of it.

Reply
0 Kudos
esiebert7625
Immortal
Immortal

That all looks correct, you might check the ESX server logs to see if there are any errors. Also try un-checking the box, saving it then going back in and checking it again.

• You can check several log files on the ESX server based on the problem you are experiencing, these include:

o Vmkernel - /var/log/vmkernel – records activities related to the virtual machines and ESX server

o Vmkernel Warnings - /var/log/vmkwarning – records activities with the virtual machines

o Vmkernel Summary - /var/log/vmksummary - Used to determine uptime and availability statistics for ESX Server; human-readable summary found in /var/log/vmksummary.txt

o ESX Server host agent log - /var/log/vmware/hostd.log - Contains information on the agent that manages and configures the ESX Server host and its virtual machines (Search the file date/time stamps to find the log file it is currently outputting to.)

o Service Console - /var/log/messages - Contain all general log messages used to troubleshoot virtual machines or ESX Server

o Web Access - /var/log/vmware/webAccess - Records information on Web-based access to ESX Server

o Authentication log - /var/log/secure - Contains records of connections that require authentication, such as VMware daemons and actions initiated by the xinetd daemon.

o VirtualCenter agent - /var/log/vmware/vpx - Contains information on the agent that communicates with VirtualCenter

o Virtual Machines - The same directory as the affected virtual machine’s configuration files; named vmware.log - Contain information when a virtual machine crashes or ends abnormally

Reply
0 Kudos
gjbird
Contributor
Contributor

Tried the obvious of unchek/recheck (and even tried that with a reboot inbetween as well)

Will start going through all those log files, but I'm not a linux/unix (or whatever it runs on), so will take a little time

Thanks

Reply
0 Kudos
esiebert7625
Immortal
Immortal

Easiest way is to log in via the SC and use Nano to open the log file, otherwise use WinSCP to connect to the ESX server from your workstation and open the files that way. It's a Windows Explorer like UI and you can edit the files with it.

WinScp (file transfer) - http://winscp.net/eng/index.php

Reply
0 Kudos
scottmlew
Enthusiast
Enthusiast

I'm seeing the same issue, but only after the 3.0.2 update. Previously, my machines all powered up just fine after reboot, although they never powered down correctly on shutdown (so I had created a script to do that for me). But now, neither works...very annoying. The auto start functionality is critical IMHO.

I've just started to work on this issue as I first observed it yesterday...if I get insight I'll post, and if anyone has ideas, PLMK!

p.s. the first time I rebooted after installing the 3.0.2 update, approximately the first half of my machines DID auto start. When I saw that I rebooted again, and then nothing started, and nothing has started since. I wonder if that odd behavior provides a clue to anyone with more experience in this area?

Reply
0 Kudos
esiebert7625
Immortal
Immortal

I'd open a support ticket with VMware, if this is a bug with 3.0.2 they should now about it so they can get it fixed.

Reply
0 Kudos
gjbird
Contributor
Contributor

This is 3.0.2 that I'm using, so there may be something in that. Also, I remember that I tried to set the boot order using Virtual Center, but it failed, saying something about not being able to set it, but when I pointed Infrastructure client directly at the ESX box, it said it did set it (even though it didn't work).

So could it be something to do with Virtual Center screwing up the config?

Reply
0 Kudos
gjbird
Contributor
Contributor

An update of some testing

Original server that wasn't working was built directly from the 3.0.2 CD, so I trashes that and then rebuilt the server from scratch, using 3.0.0, machines autostarted correctly (although didnt shutdown correctly).

Then I Upgraded to 3.0.2, still autostarted correctly.

Trashes the setup again, and this time did the install directly from the 3.0.2 CD again, autostart FAILS!

So I'd say that there is a bug in 3.0.2 when built directly from that version.

As I'm only on a trial license, and an old Dell (that probably isn't on the officially supported list) any suggestions on how I go reporting this to VMWare?

Reply
0 Kudos
gjbird
Contributor
Contributor

Support feedback form filled in, will await a patch.

Reply
0 Kudos
gjbird
Contributor
Contributor

The plot thickens,

Server Built 3.0.0, autostart works

Upgrade to 3.0.2 autostart still works

add additional guest to server, add it to autostart, reboot server and.....

autostart now fails for ALL guests (including the ones that were working)

removed the additional guest, in effect, putting the autostart config back to how it was, and autostart works again!

Reply
0 Kudos
esiebert7625
Immortal
Immortal

Sounds like a bug, at least it is easily re-producible.

Reply
0 Kudos