VMware Cloud Community
w6vms
Contributor
Contributor

Virtual machine auto-start

I have several VM's, all running FreeBSD 8.0-RELEASE, and upon restarting the ESXi 4.0 host, none of the VM's

automatically start, even though they are all configured to do so.

Any ideas?

I did install the open source virtual machine tools (open-vm-tools port) on all of the VM's (I have not been able to find a release of VMWare Tools for FreeBSD 8.0, does this exist?)

Thanks!

0 Kudos
9 Replies
Troy_Clavell
Immortal
Immortal

In the Virtual Machine Startup/Shutdown options you have guests that are in the "Automatic Startup" list? Also, are you using vCenter to manage these guests in an HA cluster, or just a standaone ESXi4 Host?

0 Kudos
w6vms
Contributor
Contributor

Yes, the VM's are in the automatic startup list, that is what I meant by being configured to auto-start.

I am not using vCenter, this is just a standalone ESXi4 host.

0 Kudos
Troy_Clavell
Immortal
Immortal

since you are running a non-supported guest OS, and the tools are not from the ESXi Host, my guess is this is part of the problem. Can you deploy a supported guest OS, install the tools that are supplied by your ESXi Host and put that guest in the startup order and see if it works?

http://www.vmware.com/pdf/GuestOS_guide.pdf

0 Kudos
w6vms
Contributor
Contributor

No, I am sure that will work fine, I am trying to get this to work with FreeBSD 8.0 VM's.

0 Kudos
Troy_Clavell
Immortal
Immortal

I don't have an answer then, your running a non-supported guest, on non-supported tools. There in-lays the problem.

0 Kudos
w6vms
Contributor
Contributor

The VM's aren't even powered up. How would the presence of VMWare Tools have an effect on this?

0 Kudos
golddiggie
Champion
Champion

A quick jog into the 'help' menu item, and searching mildly, yielded more information about the VMware tools... From my understanding of the VMware Tools, it ties into the virtual hardware of the VM. Meaning that without said tools, you won't have the 'bare metal' management of the VM that you would with the tools installed/running. That is on top of providing better drivers/support for the virtual hardware than without the tools.

Since you're running off the reservation with your combination of VM OS and set of tools, there's not a lot that can be done from this side of things. I would suggest checking with the people who created the tools you installed to see if they have a patch, fix, or line of code you can insert to gain the additional functionality you're looking for.

Otherwise, the best you can probably hope for is to set up alerts (email notifications) for when the VM goes down, and doesn't come back online within X minutes. This way you at least know the VM is not starting up and can address that issue more rapidly.

0 Kudos
naptrel
Contributor
Contributor

I stumbled across your post because I've been having similar problems, and also happen to be running a FreeBSD 8 guest OS, but on ESXi 3.5 (as well as other OSes).

I eventually found my solution by looking through log files that I didn't really understand: Auto-start of virtual machines won't work if you're running a single ESXi host upon which you have Lockdown Mode enabled. Turning Lockdown Mode off solved my problems.

And don't listen to 'em: FreeBSD is a great OS and works fine for me even without VMWare tools installed.

Nathaniel

0 Kudos
w6vms
Contributor
Contributor

I am now using the VMWare tools that support FreeBSD 8.0, and have been doing more testing.

If the VM is stored on a local disk, it autostarts just fine.

If the VM is stored on an NFS server, autostarts does not work. This is true of both FreeBSD 8.0 and version of Ubuntu on the supported list, with VMWare tools installed.

0 Kudos