Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm testing ESXi 5.0U1 on a small box. One VM for testing and all setup for auto start VM on boot but the VM don't come up.

enter image description here

share|improve this question
up vote 9 down vote accepted

If this is Esxi 5.0U1 with the free license, autostarting VMs is known broken.

share|improve this answer
Good to know. I got vmware -l = VMware ESXi 5.0.0 Update 1 . Any reference ? – PeterMmm May 24 '12 at 7:57

Like @rackandboneman says, ESXi 5.0U1 with the free licence broke autostart of VMs. I updated, but had to roll back, because I rely on autostart. Here's a thread on HardForum where a VMware employee (lopoetve) confirms it:

Here's an official blog post confirming the issue, and explaining it in more detail, aswell as rollback guide:

If you are running the free version of ESXi (aka ESXi Hypervisor) then you'll want to be aware of a critical issue that surfaces after upgrading to 5.0 Update 1. I want to stress this only applies to people runing the free ESXi version. If you're ESXi hosts are licensed this issue does not affect you.

There were some changes made in the way the ESXi APIs are accessed in Update 1 that unfortunately breaks the VM Auto Start feature in the free ESXi version. Please note that this issue only affects the free ESXi version and it was not intentional.

More detailed rollback guide: (Do at your own risk!)

share|improve this answer
One could use vim-cmd in a script started from rc.local if really needed. But then, in the small environments you use ESXi free in autostart is overrated - if you are doing maintenance then start your VMs when its over, if the machine crashes with a PSOD or hang or reboots spontaneously you want to do a modicum of investigation before letting a stampede of VMs loose on a damaged machine. – rackandboneman May 24 '12 at 8:06
But it will be very helpful in a small environment after powerfail. I ended up with yours in rc.local adding lines like this (sleep 30;vim-cmd vmsvc/power.on 8) & – PeterMmm Jun 28 '12 at 13:53

I wrote a blog post a couple of days ago that has a workaround for this. Hopefully someone will find it useful :)

share|improve this answer
That link is broken: "Este sitio ha sido suspendido." – Rob Kennedy Jan 10 '14 at 20:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.