VMotion Disabled After ESX Server Patch Upgrade or Boot into Linux
Details
I used a patch to upgrade my ESX Server. I booted into Linux, then
booted back to vmnix. My VMotion is now disabled. What happened?
Solution
VMotion may become disabled after you use an ESX Server patch
upgrade, or after you boot an ESX Server host into Linux mode and
boot it back to vmnix mode while VirtualCenter is connected to the
host.
There are two workarounds:
Disconnect the ESX Server host from VirtualCenter before
applying the ESX Server patch upgrade or booting the ESX Server
host in Linux mode.
Disable xinetd before upgrading or booting to the
plain Linux mode, and enable xinetd after.
To disable xinetd:
Turn off run level 3 of the xinetd daemon using
chkconfig when you boot into Linux mode.
Set xinetd to not start after booting.
Set chkconfig level 3 xinetd to off.
Boot into Linux mode.
Set xinetd to start after booting.
Set chkconfig level 3 xinetd to on.
Boot into vmnix mode.
These workarounds apply to ESX Server versions 2.5.3, 2.5.1, 2.5,
and 2.0.1.
