vMotion Turns off every host reboot.

[gkris]

For some reason vMotion turns itself off if a host dies/turns off/needs to be rebooted.

How do I make it stay on forever?

[SyApps]

What do you mean when you say vmotion turns itself off? What becomes unavailable and what do you have to do to turn it back on? Reconfigure HA?

[idle-jam]

hardly heard of such occurrence that vmotion is being disable after a reboot, can you check if your host has sufficient free space. also can you describe in more details on your problem?

[AndreTheGiant]

vMotion can be enabled/disable with an advanced option at host level. Do you mean this?

But usually there is no reason to modify this setting.

Andre

[bulletprooffool]

gkris - this is probably related to your inability to enable EVC on your cluster - I think you have incompatible CPUs in yur cluster and thus VMs can not vMotion without being restarted.(so cold vMotion really)

[gkris]

Thanks for the replies, I'm still having this issue. It's not related to EVC since I got this turned on.

I have ample free space on the data stores. However could it be related to me using IBM servers with a USB Key as the place where the hypervisor is on?

[Dave_Mishchenko]

This is a known issue with 4.1 U1 - http://www.vmware.com/support/vsphere4/doc/vsp_esxi41_u1_rel_notes.html#knownissues.

vMotion is disabled after a reboot of ESXi 4.1 host
If you enable vMotion on an ESXi host and reboot the ESXi host, vMotion is no longer enabled after the reboot process is completed.

Workaround: To resolve the issue, reinstall the latest version of ESXi image provided by your system vendor.

Dave
VMware Communities User Moderator

Free ESXi Essentials training / eBook offer

Now available - VMware ESXi: Planning, Implementation, and Security

Also available - vSphere Quick Start Guide